[323717] Cleaning up vex-dev branch and then will merge to vex-release
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.project b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.project
deleted file mode 100644
index 82a27bb..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.project
+++ /dev/null
@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<projectDescription>

-	<name>org.eclipse.wst.xml.security.doc</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/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.settings/org.eclipse.core.resources.prefs b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.settings/org.eclipse.core.resources.prefs
deleted file mode 100644
index 54f5ed0..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/.settings/org.eclipse.core.resources.prefs
+++ /dev/null
@@ -1,28 +0,0 @@
-#Sun May 09 19:09:28 CEST 2010
-eclipse.preferences.version=1
-encoding//html/canonicalization/canonicalize.html=utf-8
-encoding//html/contents.html=utf-8
-encoding//html/decryption/decrypt.html=utf-8
-encoding//html/decryption/page_open_a_key.html=utf-8
-encoding//html/decryption/page_resource.html=utf-8
-encoding//html/encryption/encrypt.html=utf-8
-encoding//html/encryption/page_algorithms.html=utf-8
-encoding//html/encryption/page_create_key.html=utf-8
-encoding//html/encryption/page_create_keystore.html=utf-8
-encoding//html/encryption/page_keys.html=utf-8
-encoding//html/encryption/page_open_key.html=utf-8
-encoding//html/encryption/page_resource.html=utf-8
-encoding//html/overview/overview.html=utf-8
-encoding//html/overview/tasks.html=utf-8
-encoding//html/preferences/encryption.html=utf-8
-encoding//html/preferences/general.html=utf-8
-encoding//html/preferences/signature.html=utf-8
-encoding//html/quickfunctions/quickfunctions.html=utf-8
-encoding//html/signature/page_algorithms.html=utf-8
-encoding//html/signature/page_create_key.html=utf-8
-encoding//html/signature/page_create_keystore.html=utf-8
-encoding//html/signature/page_keys.html=utf-8
-encoding//html/signature/page_open_key.html=utf-8
-encoding//html/signature/page_resource.html=utf-8
-encoding//html/signature/sign.html=utf-8
-encoding//html/verification/verify.html=utf-8
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/META-INF/MANIFEST.MF b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/META-INF/MANIFEST.MF
deleted file mode 100644
index 3f3fa97..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/META-INF/MANIFEST.MF
+++ /dev/null
@@ -1,9 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %bundleName
-Bundle-SymbolicName: org.eclipse.wst.xml.security.doc;singleton:=true
-Bundle-Version: 0.5.0.qualifier
-Bundle-Vendor: %bundleProvider
-Bundle-Localization: plugin
-Bundle-RequiredExecutionEnvironment: J2SE-1.5
-Require-Bundle: org.eclipse.ui.cheatsheets
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/about.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/about.html
deleted file mode 100644
index 9f954c7..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/about.html
+++ /dev/null
@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<HTML>
-
-<head>
-<title>About</title>
-<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-</head>
-
-<BODY lang="EN-US">
-
-<H3>About This Content</H3>
-
-<P>March, 2009</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/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</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&apos;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>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/build.properties b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/build.properties
deleted file mode 100644
index 60862d0..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/build.properties
+++ /dev/null
@@ -1,18 +0,0 @@
-###############################################################################
-# Copyright (c) 2009 Dominik Schadow - http://www.xml-sicherheit.de
-# 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:
-#     Dominik Schadow - initial API and implementation
-###############################################################################
-bin.includes = META-INF/,\
-               *.css,\
-               *.xml,\
-               *.html,\
-               plugin.properties,\
-               cheatsheets/,\
-               html/
-generateSourceBundle=false
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/decrypt.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/decrypt.xml
deleted file mode 100644
index 3153389..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/decrypt.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="XML Decryption">
-   <intro href="/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html">
-      <description>
-         Welcome to the <b>XML Decryption</b> tutorial for the <b>XML Security Tools</b>.<br/>
-This tutorial will show you step by step how to decrypt an arbitrary XML document using the <b>XML Decryption Wizard</b>.<br/>
-To start this tutorial click the <b>Click to Begin</b> button below. You need an encrypted XML document to proceed.<br/>
-By the way, this tutorial shows only some possibilities of the XML Decryption Wizard. You can find more information in the extensive online help.
-      </description>
-   </intro>
-   <item title="Open an encrypted XML document" skip="true" href="/org.eclipse.platform.doc.user/tasks/tasks-46.htm">
-      <description>
-         Open an encrypted XML document (you may have created with the <b>XML Encryption Wizard</b>). You can skip this item if your encrypted XML document is already opened in an editor.
-      </description>
-   </item>
-   <item title="Decrypt the document" skip="false" href="/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html">
-      <description>
-         Now it&apos;s time to actually decrypt your XML document. Start the <b>XML Decryption Wizard</b> by clicking on <b>New Decryption...</b> in the context menu <b>XML Security</b>. The wizard consists of one page.<br/>
-On this page you have to select the keystore containing the used key (you may have created this keystore in the <b>XML Encryption Wizard</b>) and enter the used key. Both, keystore and key, may require a password which you have to enter as well. After that you can select an encryption ID in the <b>Encryption ID</b> drop down box. In case there are no encryption IDs contained in the XML document you can only select to encrypt the first discovered encryption in the document.<br/>
-Your XML document will be decrypted after clicking on <b>Finish</b>. If not you may have entered some incorrect information in the wizard. In this case launch the wizard again and enter the correct information.
-	  </description>
-   </item>
-</cheatsheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/encrypt.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/encrypt.xml
deleted file mode 100644
index 21a5fab..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/encrypt.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="XML Encryption">
-   <intro href="/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html">
-      <description>
-         Welcome to the <b>XML Encryption</b> tutorial for the <b>XML Security Tools</b>.<br/>
-This tutorial will show you step by step how to encrypt an arbitrary XML document using the <b>XML Encryption Wizard</b>.<br/>
-You will create a project and an XML document to encrypt. To start this tutorial click the <b>Click to Begin</b> button below. You can skip the first step if you already have a project and an opened XML document.<br/>
-By the way, this tutorial shows only some possibilities of the XML Encryption Wizard. You can find more information in the extensive online help.
-      </description>
-   </intro>
-   <item title="Create a new project and sample document" dialog="true" skip="true" href="/org.eclipse.platform.doc.user/tasks/tasks-42.htm">
-      <description>
-         The first step is to create a new project (your XML documents must be part of a project to work properly with the XML Security Tools). It doesn&apos;t matter what type of project, the best type is of course an XML project. After that create a new XML document with arbitrary elements, attributes and everything you want to encrypt.<br/>
-It is advisable to start with a small XML document and to extend it step by step. You can create a sample project and a sample XML document automatically by clicking on the <b>Click to perform</b> link below. You can skip this step (<b>Click to skip</b> link) if you already have a project and a contained XML document.
-      </description>
-      <action class="org.eclipse.wst.xml.security.ui.cheatsheets.CreateSampleProject" pluginId="org.eclipse.wst.xml.security.ui" confirm="false">
-      </action>
-   </item>
-   <item title="Resource and Encryption Type" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/encryption/page_resource.html">
-      <description>
-         Now it&apos;s time to actually encrypt your XML document. Start the <b>XML Encryption Wizard</b> by clicking on <b>New Encryption...</b> in the context menu <b>XML Security</b>. The wizard consists of three pages.<br/>
-On the first page you have to select the resource you want to encrypt (the complete document, a text selection or a node defined by an XPath expression). In order to encrypt a text selection you must select a well-formed part of your XML document before you start the wizard.<br/>
-Select the encryption type: Enveloping or detached. Enveloping encrypts the active document, whereas detached encrypts the specified document in the textfield.<br/>
-Finally choose a keystore and key option: The wizard enables you to use an existing key, create a new one or even create a new keystore together with a new key. The following wizard page depends on your selection here and will either require to select a keystore/ key or to enter the necessary information to create a new one.
-      </description>
-   </item>
-   <item title="Keystore and Key" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/encryption/page_keys.html">
-      <description>
-         You can use an existing key in a Java Keystore (*.jks) and continue the encryption process with it. To create a new key enter all data, select a key type and click the <b>Generate</b> button.<br/>
-In future encryption sessions you can reuse this keystore and key and must only enter the keystore and key passwords. A newly generated keystore is stored in the current project folder and any new key will be used in the active encryption process.
-      </description>
-   </item>
-   <item title="Algorithms and Encryption Properties" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html">
-      <description>
-         On the last page of the Encryption Wizard you have to select different algorithms and some optional properties.<br/>
-By activating &apos;Encrypt only element content&apos; the root element of your document (or selection) will remain as plain text. Finally you can enter an id to identify your encryption (recommended).<br/>
-By selecting the &apos;Start XML Signature Wizard afterwards&apos; checkbox the XML Signature Wizard will be called after the signature is created.<br/>
-The document will be encrypted after clicking on &apos;Finish&apos;.
-      </description>
-   </item>
-</cheatsheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/quick.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/quick.xml
deleted file mode 100644
index 494a60f..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/quick.xml
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="XML Quick...">
-   <intro href="/org.eclipse.wst.xml.security.doc/html/quickfunctions/quickfunctions.html">
-      <description>
-         Welcome to the <b>XML Quick Functions</b> tutorial for the <b>XML Security Tools</b>.<br/>
-This tutorial will show you the general usage of the different quick functions. You will enter the necessary information on the preference pages to activate these functions and to get an overview of all possibilities. To start this tutorial click the <b>Click to Begin</b> link below.<br/>
-By the way, this tutorial shows only some possibilities of the XML Quick Functions. You can find more information in the extensive online help.
-      </description>
-   </intro>
-   <item title="Preferences" dialog="true" skip="true" href="/org.eclipse.wst.xml.security.doc/html/preferences/general.html">
-      <description>
-         The first required step is to provide the necessary information in your workspace preferences. You have to enter all information normally provided in the respective wizard (except passwords).<br/>
-You can skip this item if you already entered this information.
-      </description>
-      <action class="org.eclipse.wst.xml.security.ui.cheatsheets.OpenPreferences" pluginId="org.eclipse.wst.xml.security.ui" confirm="false">
-      </action>
-   </item>
-   <item title="Create a new project and sample document" dialog="true" skip="true" href="/org.eclipse.platform.doc.user/tasks/tasks-42.htm">
-      <description>
-         The first step is to create a new project (your XML documents must be part of a project to work properly with the XML Security Tools). It doesn&apos;t matter what type of project, the best type is of course an XML project. After that create a new XML document with arbitrary elements, attributes and everything you want to encrypt.<br/>
-It is advisable to start with a small XML document and to extend it step by step. You can create a sample project and a sample XML document automatically by clicking on the <b>Click to perform</b> link below. You can skip this step (<b>Click to skip</b> link) if you already have a project and a contained XML document.
-      </description>
-      <action class="org.eclipse.wst.xml.security.ui.cheatsheets.CreateSampleProject" pluginId="org.eclipse.wst.xml.security.ui" confirm="false">
-      </action>
-   </item>
-   <item title="Quick functions" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/quickfunctions/quickfunctions.html">
-      <description>
-         You are now ready to use a quick function: right click in the (XML) editor, select <b>XML Security</b> in the context menu and click on any of the quick functions provided (<b>Quick [Signature | Verification | Encryption | Decryption]</b>).<br/>
-All following steps depend on the selected quick function. Some functions ask you to enter sensitive data (like passwords in <b>Quick Signature</b>); some don&apos;t and show the result directly (like <b>Quick Verification</b>).<br/>
-If required preferences are missing a dialog will inform you. You can then provide the missing information directly in the dialog by clicking on the link or skip the action.
-      </description>
-   </item>
-</cheatsheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/sign.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/sign.xml
deleted file mode 100644
index db522e0..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/sign.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="XML Signature">
-   <intro href="/org.eclipse.wst.xml.security.doc/html/signature/sign.html">
-      <description>
-         Welcome to the <b>XML Signature</b> tutorial for the <b>XML Security Tools</b>.<br/>
-This tutorial will show you step by step how to sign an arbitrary XML document using the <b>XML Signature Wizard</b>.<br/>
-You will create a project and an XML document to sign To start this tutorial click the <b>Click to Begin</b> button below. You can skip the first step if you already have a project and an opened XML document.<br/>
-By the way, this tutorial shows only some possibilities of the XML Signature Wizard. You can find more information in the extensive online help.
-      </description>
-   </intro>
-   <item title="Create a new project and sample document" dialog="true" skip="true" href="/org.eclipse.platform.doc.user/tasks/tasks-42.htm">
-      <description>
-         The first step is to create a new project (your XML documents must be part of a project to work properly with the XML Security Tools). It doesn&apos;t matter what type of project, the best type is of course an XML project. After that create a new XML document with arbitrary elements, attributes and everything you want to encrypt.<br/>
-It is advisable to start with a small XML document and to extend it step by step. You can create a sample project and a sample XML document automatically by clicking on the <b>Click to perform</b> link below. You can skip this step (<b>Click to skip</b> link) if you already have a project and a contained XML document.
-      </description>
-      <action class="org.eclipse.wst.xml.security.ui.cheatsheets.CreateSampleProject" pluginId="org.eclipse.wst.xml.security.ui" confirm="false">
-      </action>
-   </item>
-   <item title="Resource and Signature Type" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/signature/page_resource.html">
-      <description>
-         Now it&apos;s time to actually sign your XML document. Start the <b>XML Signature Wizard</b> by clicking on <b>New Signature...</b> in the context menu <b>XML Security</b>. The wizard consists of three pages.<br/>
-On the first page you have to select the resource you want to sign (the complete document, a text selection or a node defined by an XPath expression). In order to sign a text selection you must select a well-formed part of your XML document before you start the wizard.<br/>
-After that you have to select which signature type you want to use (enveloping, enveloped or detached).<br/>
-Finally choose a keystore and key option: The wizard enables you to use an existing key, create a new one or even create a new keystore together with a new key. The following wizard page depends on your selection here and will either require to select a keystore/ key or to enter the necessary information to create a new one.
-      </description>
-   </item>
-   <item title="Keystore and Key" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/signature/page_keys.html">
-      <description>
-         You can use an existing key in a Java Keystore (*.jks) and continue the signature process with it. To create a new key enter all data, select a key type and click the <b>Generate</b> button.<br/>
-In future signing sessions you can reuse this keystore and key and must only enter the keystore and key passwords. A newly generated keystore is stored in the current project folder and any new key will be used in the active signature process.
-      </description>
-   </item>
-   <item title="Algorithms and Signature Properties" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html">
-      <description>
-         The last page of the XML Signature Wizard requires the algorithms selections for the signature as well as the canonicalization and transformation algorithms. You must select an algorithm in every field.<br/>

-You can only use RSA algorithms with a RSA keystore and DSA algorithms with a DSA keystore.<br/>

-The Signature Properties are optional and can extend a signature with arbitrary information.<br/>

-At last you can enter an id to identify your signature (strongly recommended for verification).<br/>

-By selecting the &apos;Start Encryption Wizard afterwards&apos; checkbox the XML Encryption Wizard will be called after the signature is created.<br/>

-After providing all required information you can sign the document by clicking on the &apos;Finish&apos; button.
-      </description>
-   </item>
-</cheatsheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/verify.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/verify.xml
deleted file mode 100644
index 3cb06de..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/cheatsheets/verify.xml
+++ /dev/null
@@ -1,23 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<cheatsheet title="XML Verification">
-   <intro href="/org.eclipse.wst.xml.security.doc/html/verification/verify.html">
-      <description>
-         Welcome to the <b>XML Verification</b> tutorial for the <b>XML Security Tools</b>.<br/>
-This tutorial will show you step by step how to verify one or more XML signatures using the <b>XML Signatures View</b>.<br/>
-In this cheat sheet you will open a signed XML document and then verify all contained signatures in this document. To start this tutorial click the <b>Click to Begin</b> link below.<br/>
-By the way, this tutorial shows only some possibilities of the XML Signatures View. You can find more information in the extensive online help.
-      </description>
-   </intro>
-   <item title="Open a signed XML document" dialog="true" skip="true" href="/org.eclipse.platform.doc.user/tasks/tasks-46.htm">
-      <description>
-         Open an arbitrary XML document containing at least one signature (you may have created with the <b>XML Signature Wizard</b> before). You can skip this item if your signed XML document is already opened in an editor.
-      </description>
-   </item>
-   <item title="Verify the signatures" dialog="true" skip="false" href="/org.eclipse.wst.xml.security.doc/html/verification/verify.html">
-      <description>
-         Open the <b>XML Signatures View</b>: right click in the (XML) editor, select <b>XML Security</b> in the context menu and click on <b>New Verification...</b>. A new view <b>XML Signatures</b> appears containing various numbers of entries (depending on the amount of signatures in your XML document).<br/>
-This view contains four columns: The first one indicates the signature status by color. Green is a valid signature, red an invalid. A yellow marked signature could not be verified. The following columns contain the signature id, the certificate type and the certificate algorithm.<br/>
-You can show additional information on the selected signature by selecting the corresponding signature and clicking on the <b>Properties</b> (icon or menu of the view). The top status line in the view informs you about the number of signatures found in the selected XML document and their status.
-      </description>
-   </item>
-</cheatsheet>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/contexts.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/contexts.xml
deleted file mode 100644
index 123e839..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/contexts.xml
+++ /dev/null
@@ -1,92 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<contexts>
-	<context id="wizard_signature_resource">
-		<description>Select a &lt;b&gt;resource&lt;/b&gt; to sign (the complete document or a fragment of it), the &lt;b&gt;signature type&lt;/b&gt; (enveloping, enveloped or detached) and a &lt;b&gt;key option&lt;/b&gt; (create a new one or use an existing one). The &lt;b&gt;Basic Security Profile&lt;/b&gt; option increases interoperability of Web Service Security.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/signature/page_resource.html" label="Resource and Signature Type"/>
-	</context>
-	<context id="wizard_signature_open_key">
-		<description>Provide all required information for the &lt;b&gt;key to use&lt;/b&gt; in the current signing process.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/signature/page_open_key.html" label="Open a key"/>
-	</context>
-	<context id="wizard_signature_create_key">
-		<description>Provide all required information to &lt;b&gt;insert a new key&lt;/b&gt; into a keystore. This key will be used in the current signing process and is stored in the selected keystore.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/signature/page_create_key.html" label="Create a key"/>
-	</context>
-	<context id="wizard_signature_create_keystore">
-		<description>Provide all required information to &lt;b&gt;create a new keystore&lt;/b&gt; together with &lt;b&gt;a new key&lt;/b&gt;. This key will be used in the current signing process and is stored in the current project folder as [Keystore Name].jks.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/signature/page_create_keystore.html" label="Create a keystore and key"/>
-	</context>
-	<context id="wizard_signature_algorithms">
-		<description>Select a &lt;b&gt;canonicalization and a transformation algorithm&lt;/b&gt;, a &lt;b&gt;message digest and a signature algorithm&lt;/b&gt;. The &lt;b&gt;signature properties&lt;/b&gt; are optional. A new property can be added by clicking on the + button. The &lt;b&gt;signature id&lt;/b&gt; is optional but makes it much easier to identify the signature. The characters &lt;, &gt;, &amp;, &quot;, &apos; and blanks are not allowed as id (signature id and signature property id), the maximum length is 20 characters. Selecting the &lt;b&gt;Start Encryption Wizard afterwards&lt;/b&gt; checkbox opens the Encryption Wizard after a successful digital signature operation.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/signature/page_algorithms.html" label="Algorithms and Signature Properties"/>
-	</context>
-	<context id="wizard_encryption_resource" title="Resource and Encryption Type">
-		<description>Select the &lt;b&gt;resource&lt;/b&gt; to encrypt (the complete document or a fragment of it), the &lt;b&gt;encryption type&lt;/b&gt; (enveloping or detached) and a &lt;b&gt;key option&lt;/b&gt; (use an existing one, insert a new key in a keystore, create a new keystore and a new key). The &lt;b&gt;Basic Security Profile&lt;/b&gt; option increases interoperability of Web Service Security.</description>
-		<topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-		<topic href="html/encryption/page_resource.html" label="Resource and Encryption Type"/>
-	</context>
-    <context id="wizard_encryption_open_key" title="Use a key from an existing keystore">
-        <description>Use an existing key in the active encryption process. Provide all required information for this key and continue to the last wizard page.</description>
-        <topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-        <topic href="html/encryption/page_open_key.html" label="Use a key from an existing keystore"/>
-    </context>
-    <context id="wizard_encryption_create_key" title="Insert a new key in an existing keystore">
-        <description>Create a new key for the active encryption process. Provide all required information and insert the new key into an existing keystore and continue to the last wizard page.</description>
-        <topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-        <topic href="html/encryption/page_create_key.html" label="Insert a new key in an existing keystore"/>
-    </context>
-    <context id="wizard_encryption_create_keystore" title="Create a new key and a new keystore">
-        <description>Create a new keystore and insert a new key to use in the active encryption process. Provide all required information and continue to the last wizard page.&lt;br&gt;
-The keystore will be stored in the current (project) folder as [Keystore Name].jks.</description>
-        <topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-        <topic href="html/encryption/page_create_keystore.html" label="Create a new key and a new keystore"/>
-    </context>
-	<context id="wizard_encryption_algorithms" title="Algorithms and Encryption Properties">
-		<description>Select the &lt;b&gt;encryption algorithms&lt;/b&gt; and decide whether you want to completely encrypt the XML data or keep the root element as plain text. The &lt;b&gt;encryption id&lt;/b&gt; is optional but makes it much easier to identify the encryption. The characters &lt;, &gt;, &amp;, &quot;, &apos; and blanks are not allowed as id, the maximum length is 20 characters. Selecting the &lt;b&gt;Start Digital Signature Wizard afterwards&lt;/b&gt; checkbox opens the &lt;b&gt;XML Signature Wizard&lt;/b&gt; after a successful encryption operation.</description>
-		<topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-		<topic href="html/encryption/page_algorithms.html" label="Algorithms and Encryption Properties"/>
-	</context>
-	<context id="xpath_dialog">
-		<description>This dialog displays all XML elements in the active XML document as unique XPath expressions. You can select exactly one element you want to use in the current signing or encrypting process.</description>
-		<topic href="html/signature/sign.html" label="XML Signature Wizard"/>
-		<topic href="html/encryption/encrypt.html" label="XML Encryption Wizard"/>
-	</context>
-	<context id="wizard_decryption_resource" title="Encryption Type and ID">
-		<description>If you didn&apos;t enter an &lt;b&gt;encryption id&lt;/b&gt; during the encryption process you can only select to decrypt the first encrypted data found in the selected document. Otherwise select the desired encryption id.
-
-Select the encryption type (enveloping or detached). Selecting detached starts to search the selected encryption (identified by the id) for the reference to the detached file. This URI information is displayed below.
-
-Click &lt;b&gt;Next&lt;/b&gt; to continue to the next wizard page.</description>
-		<topic href="html/decryption/decrypt.html" label="XML Decryption Wizard"/>
-		<topic href="html/decryption/page_resource.html" label="Resource"/>
-	</context>
-    <context id="wizard_decryption_keystore" title="Encryption Keystore and Key">
-       <description>Select the &lt;b&gt;Keystore&lt;/b&gt; used for encrypting this document (-fragment) and enter the &lt;b&gt;password&lt;/b&gt; for the store. Provide the &lt;b&gt;key name&lt;/b&gt; and enter the corresponding &lt;b&gt;password&lt;/b&gt;. Click &lt;b&gt;Next&lt;/b&gt; to start the decryption process.</description>
-       <topic href="html/decryption/decrypt.html" label="XML Decryption Wizard"/>
-       <topic href="html/decryption/page_open_a_key.html" label="Open a key"/>
-    </context>
-	<context id="preferences_general">
-		<description>This preference page allows you to configure the general preferences of the &lt;b&gt;XML Security Tools&lt;/b&gt; including &lt;b&gt;Canonicalization&lt;/b&gt; settings.</description>
-		<topic href="html/canonicalization/canonicalize.html" label="Canonicalization"/>
-		<topic href="html/preferences/general.html" label="XML Security Tools Preferences"/>
-	</context>
-	<context id="preferences_signature">
-		<description>This preference page allows you to configure the preferences for the &lt;b&gt;Quick Signature&lt;/b&gt; and &lt;b&gt;Quick Verification&lt;/b&gt; functionality of the &lt;b&gt;XML Security Tools&lt;/b&gt;.</description>
-		<topic href="html/quickfunctions/quickfunctions.html" label="Quick Signature"/>
-		<topic href="html/preferences/signature.html" label="Quick Signature Preferences"/>
-	</context>
-	<context id="preferences_encryption">
-		<description>This preference page allows you to configure the preferences for the &lt;b&gt;Quick Encryption&lt;/b&gt; and &lt;b&gt;Quick Decryption&lt;/b&gt; functionality of the &lt;b&gt;XML Security Tools&lt;/b&gt;.</description>
-		<topic href="html/quickfunctions/quickfunctions.html" label="Quick Encryption"/>
-		<topic href="html/preferences/encryption.html" label="Quick Encryption Preferences"/>
-	</context>
-    <context id="signature_view">
-        <description>This view displays all &lt;b&gt;XML Signatures&lt;/b&gt; (valid, invalid and unkown) found in the selected XML document. Click &lt;b&gt;Refresh&lt;/b&gt; for a new scan of the active XML document. Select one verification result and click &lt;b&gt;Properties&lt;/b&gt; for detailed information about the selected XML Signature.</description>
-        <topic href="html/verification/verify.html" label="XML Signatures View"/>
-    </context>
-</contexts>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/book.css b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/book.css
deleted file mode 100644
index e30f5af..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/book.css
+++ /dev/null
@@ -1,214 +0,0 @@
-p.Code {
-	display: block;
-	text-align: left;
-	text-indent: 0.00pt;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 15pt;
-	font-weight: normal;
-	font-style: normal;
-	color: #4444CC;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-	font-family: "Courier New", Courier, monospace;
-}
-
-H6.CaptionFigColumn {
-	display: block;
-	text-align: left;
-	text-indent: 0.000000pt;
-	margin-top: 3.000000pt;
-	margin-bottom: 11.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 0.000000pt;
-	font-size: 75%;
-	font-weight: bold;
-	font-style: Italic;
-	color: #000000;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
-
-p.Note {
-	display: block;
-	text-align: left;
-	text-indent: 0pt;
-	margin-top: 19.500000pt;
-	margin-bottom: 19.500000pt;
-	margin-right: 0.000000pt;
-	margin-left: 30pt;
-	font-size: 110%;
-	font-weight: normal;
-	font-style: Italic;
-	color: #000000;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
-
-EM.UILabel {
-	font-weight: Bold;
-	font-style: normal;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
-
-EM.CodeName {
-	font-weight: Bold;
-	font-style: normal;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-	font-family: "Courier New", Courier, monospace;
-}
-
-UL.NavList {
-	margin-left: 1.5em;
-	padding-left: 0px;
-	list-style-type: none;
-}
-
-body,html {
-	border: 0px
-}
-
-/* following font face declarations need to be removed for DBCS */
-body,h1,h2,h3,h4,h5,h6,p,table,td,caption,th,ul,ol,dl,li,dd,dt {
-	font-family: Arial, Helvetica, sans-serif;
-	color: #000000
-}
-
-pre,code {
-	font-family: "Courier New", Courier, monospace;
-}
-
-/* end font face declarations */
-@media print {
-	html {
-		font-size: 12pt
-	}
-}
-
-body {
-	font-size: 83%;
-	background: #FFFFFF;
-	margin-bottom: 1em
-}
-
-h1 {
-	font-size: 180%;
-	margin-top: 5px;
-	margin-bottom: 1px
-}
-
-h2 {
-	font-size: 140%;
-	margin-top: 25px;
-	margin-bottom: 3px
-}
-
-h3 {
-	font-size: 110%;
-	margin-top: 20px;
-	margin-bottom: 3px
-}
-
-h4 {
-	font-size: 100%;
-	margin-top: 20px;
-	margin-bottom: 3px;
-	font-style: italic
-}
-
-p {
-	margin-top: 10px;
-	margin-bottom: 10px
-}
-
-pre {
-	font-size: 93%;
-	margin-left: 6;
-	color: #4444CC
-}
-
-code {
-	font-size: 93%;
-}
-
-table {
-	font-size: 100%
-}  /* needed for quirks mode */
-a:link {
-	color: #0000FF
-}
-
-a:hover {
-	color: #000080
-}
-
-a:visited {
-	text-decoration: underline
-}
-
-ul {
-	margin-top: 10px;
-	margin-bottom: 10px;
-}
-
-li {
-	margin-top: 5px;
-	margin-bottom: 5px;
-}
-
-li p {
-	margin-top: 5px;
-	margin-bottom: 5px;
-}
-
-ol {
-	margin-top: 10px;
-	margin-bottom: 10px;
-}
-
-dl {
-	margin-top: 10px;
-	margin-bottom: 10px;
-}
-
-dt {
-	margin-top: 5px;
-	margin-bottom: 5px;
-	font-weight: bold;
-}
-
-dd {
-	margin-top: 5px;
-	margin-bottom: 5px;
-}
-
-strong {
-	font-weight: bold
-}
-
-em {
-	font-style: italic
-}
-
-var {
-	font-style: italic
-}
-
-div.revision {
-	border-left-style: solid;
-	border-left-width: thin;
-	border-left-color: #7B68EE;
-	padding-left: 5
-}
-
-th {
-	font-weight: bold
-}
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html
deleted file mode 100644
index a2f773d..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><p>= XML Canonicalization =</p><p>XML Canonicalization does not open any wizard or view. Instead, it directly canonicalizes (normalizes) the selected XML document (always the complete document). Depending on the selected menu entry it either maintains the comments or removes them. Removed comments are replaced by an empty line. The ''&#8218;XML Security&#8217;'&#8218; [[help/topic/org.eclipse.wst.xml.security.doc/html/preferences/general.html | preferences]] allow you to switch between &#8217;&#8218;inclusive&#8217;&#8218; and &#8217;&#8218;exclusive&#8217;' XML canonicalization, which may result into different canonicalized versions of the XML document (the differences depend on the XML document).</p><p>''&#8218;XML Canonicalization&#8217;'' always takes place when signing an XML document or verifying an XML Signature. There is no need to execute this task manually (but it does not do any damage in case you do).</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/contents.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/contents.html
deleted file mode 100644
index 77ad76f..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/contents.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="XML_Security_Tools_User_Guide">XML Security Tools User Guide</h1><p>This guide provides instructions and information on how to use the <b>XML Security Tools</b>.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html
deleted file mode 100644
index f9b44fc..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="XML_Decryption_Wizard">XML Decryption Wizard</h1><p>The <b>XML Decryption Wizard</b> consists of two pages: <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html">Resource and Decryption Type</a> and <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html">Open a Key</a>.</p><p>To launch the wizard you either have to select an encrypted XML document  in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose <b>XML Security</b> and click on <b>New Decryption...</b>.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html
deleted file mode 100644
index 51eaad9..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Openakey">Open a key</h1><p>This is the second page of the XML Decryption Wizard. You'll have to provide the keystore and key information used to encrypt the XML document (-fragment).</p><p><img align="middle" title="Use a Key from an existing Keystore" alt="Use a Key from an existing Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_2.png‎"/></p><p><b>Keystore and Key</b></p><p>Simply choose the keystore containing the used key and enter the keystore password. Type in the key name and its password.</p><p>The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html
deleted file mode 100644
index 6acbc5d..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="ResourceandDecryptionType">Resource and Decryption Type</h1><p>This is the first page of the XML Decryption Wizard. You'll have to choose the encryption you want to decrypt.</p><p><img align="middle" title="Resource and Decryption Type" alt="Resource and Decryption Type" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_1.png‎"/></p><p><b>Encryption ID</b></p><p>An XML document can contain multiple encryptions with different encryption IDs. You do not have to decrypt them in document order. Instead, you can choose which one you want to decrypt (make sure to provide the corresponding keystore and key information, otherwise decryption will fail). However, this requires an ID for the XML encryption. Since IDs are optional you can choose to decrypt the first encrypted part in the XML document instead. In case the XML document contains multiple encryptions without IDs you'll have to decrypt them step by step. In order to avoid that always provide encryption IDs when encrypting XML data.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html
deleted file mode 100644
index 652a3eb..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="XML_Encryption_Wizard">XML Encryption Wizard</h1><p>The <b>XML Encryption Wizard</b> consists of three pages, with a variable second page depending on the chosen keystore/ key option. To launch the wizard you either have to select an XML document in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose <b>XML Security</b> and click on <b>New Encryption...</b>. In order to encrypt a selected XML fragment select the desired document part in the editor and launch the wizard as described before. The selection has to exist before launching the wizard, and it has to be well-formed: in case a start-tag is selected the end-tag must be selected too. Encrypting only text-content of an element is possible too.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html
deleted file mode 100644
index 89474db..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Algorithms_and_Encryption_Properties">Algorithms and Encryption Properties</h1><p>This is the last page of the XML Encryption Wizard. You must select the Encryption and the Key Wrap Algorithms. Optional, you can select to keep the root element as plain text and you can enter an encryption ID (strongly recommended). The <b>Start Signature Wizard afterwards</b> checkbox enables you to start the signature wizard after successfully encrypting the selected XML document.</p><p><img align="middle" title="Algorithms and Encryption Properties" alt="Algorithms and Encryption Properties" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_3.png‎"/></p><p><b>Encryption and Key Wrap Algorithm</b></p><p>Choose the algorithms you want to use to encrypt the XML document (fragment) and to wrap the key. You have to select algorithms that do match with the selected key on the previous wizard page.</p><p><b>Properties</b></p><p>There is only one property available: Keep root element as plain text. This creates an encrypted XML document (fragment) with a root element in plain text. In case you selected to encrypt the whole document the documents root element will be kept as plain text. In case you selected to encrypt a document fragment only (via a text selection or an XPath expression) this will result in a plain text root element of this document fragment.</p><p><b>Encryption ID</b></p><p>The encryption ID is optional, but it is strongly required to enter one. This ID must be unique in the whole document and may not contain &lt;, >, &amp;, ' or " characters. Without an encryption ID it is only possible to decrypt the XML document step by step.</p><p><b>Signature Wizard</b></p><p>Select the checkbox in case you want to start the <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html">XML Signature Wizard</a> directly after the encryption process was successfully finished.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html
deleted file mode 100644
index 43ad1e0..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Insert_a_new_Key_in_an_existing_Keystore">Insert a new Key in an existing Keystore</h1><p><b>Insert a new Key in an existing Keystore</b> is one of the alternatives as the second wizard page. Select an existing keystore (probably one you created before with the help of the <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html">Create a new Key and a new Keystore</a> wizard) and enter the keystore password. After that simply select the desired algorithm and the algorithm size for the new key and enter a name and a password for it. Click the <b>Generate</b> button when you are done to create the new key. A short message informs you about the generation result and the <b>Next</b> button will be enabled. The key generated here will be used in the active encryption process.</p><p><img align="middle" title="Insert a new Key in an existing Keystore" alt="Insert a new Key in an existing Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2b.png‎"/></p><p>Keys must be unique inside a keystore, so the wizard verifies that the entered key name does not exist in the selected keystore.</p><p>The wizard automatically stores the entered data for the keystore path and name between sessions. Passwords are never stored and have to be entered every time.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html
deleted file mode 100644
index 58493ea..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Create_a_new_Key_and_a_new_Keystore">Create a new Key and a new Keystore</h1><p><b>Create a new Key and a new Keystore</b> is one of the alternatives as the second wizard page. This page lets you create a new keystore together with a new key. Enter the name for the keystore and the password to protect it. After that choose an algorithm and its size and enter an alias name together with a password for the key. The keystore password is used to protect the whole keystore, the key password to protect the key. Both passwords are required.</p><p>Click the <b>Generate</b> button when you are done to create the new keystore together with the key. A short message informs you about the generation result and the <b>Next</b> button will be enabled. The keystore is stored with the entered name in the active folder (normally the active project). The key generated here will be used in the active encryption process.</p><p><img align="middle" title="Create a new Key and a new Keystore" alt="Create a new Key and a new Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2c.png‎"/></p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_keys.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_keys.html
deleted file mode 100644
index ada65b2..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_keys.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Keystores_and_Keys">Keystores and Keys</h1><p>The second page of the <b>XML Encryption Wizard</b> depends on your <b>Keystore and Key</b> selection on the first wizard page. You can select to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html">Use a Key from an existing Keystore</a>, <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html">Insert a new Key in an existing Keystore</a> or to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html">Create a new Key and a new Keystore</a>.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html
deleted file mode 100644
index f1169eb..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Use_a_Key_from_an_existing_Keystore">Use a Key from an existing Keystore</h1><p><b>Use a Key from an existing Keystore</b> is one of the alternatives as the second wizard page. Simply select the keystore containing the key you want to use in the current encryption process. All data is verified, you can only switch to the next case with a correct keystore and key password as well as an existing key alias.</p><p><img align="middle" title="Use a Key from an existing Keystore" alt="Use a Key from an existing Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2a.png‎"/></p><p>The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_resource.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_resource.html
deleted file mode 100644
index 82382c1..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/encryption/page_resource.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Resource_and_Encryption_Type">Resource and Encryption Type</h1><p>This is the first page of the XML Encryption Wizard. You'll have to select the resource you want to encrypt, the encryption type, the keystore/ key option and the Basic Security Profile option.</p><p><img align="middle" title="Resource and Encryption Type" alt="Resource and Encryption Type" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_1.png‎"/></p><p><b>Resource</b></p><p>It is possible to encrypt the complete document, the selected text or a document fragment specified by an XPath expression. The complete document is always possible. For a text selection this selection has to exist before launching the wizard and it has to be well-formed. XPath is always possible too. You can either enter an XPath expression in the textfield or you can select one in the dialog after clicking on the <b>Browse...</b> button. The XPath expression has to return exactly one element or element content. Encrypting attributes is not supported.</p><p><b>Encryption Type</b></p><p>The normal encryption type is a so called enveloping encryption, where the encrypted data is contained in the original document (it replaces the plain XML). A detached encryption doesn't encrypt the XML document you have chosen. Instead the data in the specified additional file here gets encrypted. Both documents will be changed. File A remains in plain XML, but does contain the encryption information for file B that gets encrypted (a detached encryption requires the whole document to be encrypted).</p><p><b>Keystore and Key</b></p><p>The chosen option here sets the following wizard page. You can either select to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html">Use a key from an existing keystore</a>, to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html">Insert a new key in an existing keystore</a> or to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html">Create a new key and a new keystore</a>.</p><p><b>Basic Security Profile</b></p><p>A Basic Security Profile compliant XML Encryption has some restrictions in comparison to a regular XML Encryption. By activating this checkbox all options in the XML Encryption Wizard will be limited to options that are compliant to this profile. In case of the XML Encryption Wizard this only limits the available algorithms on the <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html">Algorithms and Encryption Properties</a> page.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_1.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_1.png
deleted file mode 100644
index 92cfd22..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_1.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_1.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_1.png
deleted file mode 100644
index 95aec57..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_1.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2a.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2a.png
deleted file mode 100644
index deb7390..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2a.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2b.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2b.png
deleted file mode 100644
index 1ab2508..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2b.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2c.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2c.png
deleted file mode 100644
index 47fe5a3..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2c.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_3.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_3.png
deleted file mode 100644
index cad3363..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_3.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/overview/context_menu.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/overview/context_menu.png
deleted file mode 100644
index 1b72586..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/overview/context_menu.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/encryption.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/encryption.png
deleted file mode 100644
index 44f3a8b..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/encryption.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/general.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/general.png
deleted file mode 100644
index 3362949..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/general.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/signature.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/signature.png
deleted file mode 100644
index e3db7ba..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/preferences/signature.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_1.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_1.png
deleted file mode 100644
index 15cb1bb..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_1.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2a.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2a.png
deleted file mode 100644
index 2a3f5c6..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2a.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2b.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2b.png
deleted file mode 100644
index 0f0dd14..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2b.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2c.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2c.png
deleted file mode 100644
index d0932f3..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_2c.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_3.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_3.png
deleted file mode 100644
index e8017e4..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/sign/page_3.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/verify/view.png b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/verify/view.png
deleted file mode 100644
index 86f6163..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/images/verify/view.png
+++ /dev/null
Binary files differ
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/legal.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/legal.html
deleted file mode 100644
index 3cf9b4b..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/legal.html
+++ /dev/null
@@ -1,18 +0,0 @@
-<html>
-<head>
-	<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-	<title>Notices</title>
-	<link href="book.css" rel="stylesheet" type="text/css">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-	<div class="chapter" lang="en">
-	<div class="titlepage"><div><div><h2 class="title"><a name="N1046F"></a>Notices</h2></div></div></div>
-	<p>The material in this guide is Copyright (c) Dominik Schadow and others 2009.</p>
-
-	<p>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 class="ulink" href="http://www.eclipse.org/legal/epl-v10.html" target="_top">http://www.eclipse.org/legal/epl-v10.html</a>.</p>
-
-	<p><a class="ulink" href="../about.html" target="_top">Terms and conditions regarding the use of this guide</a>.</p>
-	</div>
-</body>
-</html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/overview.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/overview.html
deleted file mode 100644
index 84a3ba1..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/overview.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Overview">Overview</h1><p><b>XML Security Tools</b> add three wizards for <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html">signing</a>, <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html">encrypting</a> and <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html">decrypting</a> various XML documents to the WTP XML editor and different views. A new view, XML Signatures, is included for <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html">verification</a> of all XML signatures in the selected XML document as well as to provide detailed information on each signature.</p><h2 id="Launching_XML_Security_Tools">Launching XML Security Tools</h2><p>To call any functionality of the XML Security Tools simply select an XML document in the <i>Navigator</i>, <i>Package Explorer</i> or <i>Project Explorer</i> view or inside the WTP XML editor and choose the desired operation in the <b>XML Security</b> entry in the context menu. The XML Security context menu inside the mentioned views is only available in the <i>XML perspective</i>. It is always available inside the WTP XML editor, no matter which perspective is active at the moment.</p><p><img align="middle" title="XML Security Tools context menu" alt="XML Security Tools context menu" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/overview/context_menu.png‎"/></p><h2 id="The_XML_Security_menu">The XML Security menu</h2><p>The XML Security menu contains ten entries. The items with an icon launch a wizard (<b>New Signature...</b>, <b>New Encryption...</b>, <b>New Decryption...</b>) or a view (<b>New Verification...</b>). The ones without any icon launch a command directly, with minimum or no user interaction at all.</p><p>There are no differences in the menu when calling it from inside the XML editor on inside a view. However there is one difference in the <b>XML Signature</b> and <b>XML Encryption</b> wizard: it is not possible to sign/ encrypt a text selection when using the context menu inside a view. The text selection has to exist before opening the wizard, which is not possible from within a view.</p><p>Calling any XML Security command from within the XML editor activates the Eclipse undo/ redo functionality. Keep that in mind since it makes it easy to undo any encryption while the editor is still open. Calling any XML Security command from within a view writes any changes directly to the selected file, without any undo/ redo possibility.</p><h2 id="Quick_Functionality">Quick Functionality</h2><p>The so called <i>Quick Functions</i> - <b>Quick Signature</b>, <b>Quick Verification</b>, <b>Quick Encryption</b> and <b>Quick Decryption</b> - require less or no user interaction at all. These commands use predefined preferences and only ask the user for security sensitive information like passwords. This is the fastest way to sign, verify, encrypt or decrypt any XML document. A dialog opens in case there are any missing preferences to continue the operation. You can either jump directly to the corresponding preference page and provide the information (like the keystore to use, the desired algorithm, signature id and so on) or cancel the complete operation.</p><p>It is possible to mix <i>normal</i> XML Security operations with the quick functions. So you can encrypt an XML document with the wizard and decrypt it using the <b>Quick Decryption</b> function. The only requirement is that the settings you have chosen in the wizard do match the preference settings for XML Decryption.</p><h2 id="XML_Security_Preferences">XML Security Preferences</h2><p>The <b>XML Security</b> preferences are available as sub-pages in the <b>XML</b> category. Three pages are available, from general settings on the <b>XML Security</b> page to specific settings for <b>Encryption</b> and <b>Signatures</b>. It is wise to define different IDs for signature and encryption, this makes verification and decryption much easier. Quick Verification and Quick Decryption may fail in case the IDs are not unique.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/tasks.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/tasks.html
deleted file mode 100644
index e71a622..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/overview/tasks.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Tasks">Tasks</h1><p>The <b>XML Security Tools</b> enable you to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html">canonicalize</a>, <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html">sign</a>, <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html">verify</a> and to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html">encrypt</a> and <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html">decrypt</a> arbitrary XML documents in your Eclipse workbench.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html
deleted file mode 100644
index f85a7dc..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Encryption_Preferences">Encryption Preferences</h1><p>All settings on this page only affect <b>Quick Encryption</b> and <b>Quick Decryption</b>, not the normal wizards. Here you can select what you want to encrypt - the whole document, a selection or a document fragment identified by an XPath expression. The encryption type is fixed to <i>Enveloping</i> at the moment. Select the algorithms to use and provide a keystore containing a key which match those algorithms. Chose the encryption id carefully. Quick Decryption searches for this id, so it should be unique.</p><p><img align="middle" title="XML Security Tools encryption preferences" alt="XML Security Tools encryption preferences" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/encryption.png‎"/></p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/general.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/general.html
deleted file mode 100644
index 243b44b..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/general.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="General_Preferences">General Preferences</h1><p>The <b>XML Security</b> preferences are available as sub-pages in the <b>XML</b> category. Three pages are available, from general settings on the <b>XML Security</b> page to specific settings for <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html">Encryption</a> and <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/preferences/signature.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/preferences/signature.html">Signatures</a>.</p><p>The general XML Security Tools preference page allows you to specify some general settings for the whole plug-in.</p><p><img align="middle" title="XML Security Tools preferences" alt="XML Security Tools preferences" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/general.png‎"/></p><p>By default, an exclusive XML canonicalization is executed when selecting on of the Canonicalization entries in the menu. Select the inclusive option in case you do require this canonicalization type. The canonicalization target is normally the same file, so the original file gets manipulated. In case you do want to keep the original file you can select to create a new document for canonicalization. This only affects canonicalization, not any of the other wizards! Creating a new file adds _canon to the filename, with additional numbering in case this file already exists.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/signature.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/signature.html
deleted file mode 100644
index 659fcd2..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/preferences/signature.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Signature_Preferences">Signature Preferences</h1><p>All settings on this page only affect <b>Quick Signature</b> and <b>Quick Verification</b>, not the normal wizard or view. Here you can select what you want to sign - the whole document, a selection or a document fragment identified by an XPath expression. The signature types <i>Enveloping</i> and <i>Enveloped</i> are available. Select the different algorithms to use and provide a keystore containing a key which match those algorithms. Chose the signature id carefully. Quick Verification searches for this id, so it should be unique.</p><p><img align="middle" title="XML Security Tools signature preferences" alt="XML Security Tools signature preferences" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/signature.png‎"/></p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/quickfunctions/quickfunctions.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/quickfunctions/quickfunctions.html
deleted file mode 100644
index 5d9c3f6..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/quickfunctions/quickfunctions.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Quick_Functions">Quick Functions</h1><p>The so called <i>Quick Functions</i> - <b>Quick Signature</b>, <b>Quick Verification</b>, <b>Quick Encryption</b> and <b>Quick Decryption</b> - require less or no user interaction at all. These commands use predefined preferences and only ask the user for security sensitive information like passwords. This is the fastest way to sign, verify, encrypt or decrypt any XML document. A dialog opens in case there are any missing <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/preferences/general.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/preferences/general.html">preferences</a> to continue the operation. You can either jump directly to the corresponding preference page and provide the information (like the keystore to use, the desired algorithm, signature id and so on) or cancel the complete operation.</p><p>It is possible to mix <i>normal</i> XML Security operations with the quick functions. So you can encrypt an XML document with the wizard and decrypt it using the <b>Quick Decryption</b> function. The only requirement is that the settings you have chosen in the wizard do match the preference settings for XML Decryption.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html
deleted file mode 100644
index 3e196cd..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><p>= Algorithms and Signature Properties =</p><p>This is the last page of the XML Signature Wizard. You must select algorithms for the message digest and the signature as well as a canonicalization and transformation algorithm. Optional, you can define some signature properties and you can enter a signature ID (strongly recommended). The ''&#8218;Start Encryption Wizard afterwards&#8217;'' checkbox enables you to start the encryption wizard after successfully signing the selected XML document.</p><p>[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_3.png‎|Algorithms and Signature Properties|center]]</p><p>''&#8218;Canonicalization and Transformation Algorithm&#8217;''</p><p>Choose the algorithms you want to use for canonicalization and transformation. Whereas canonicalization is required, the transformation algorithm can be set to '&#8218;none&#8217;'.</p><p>''&#8218;Message Digest and Signature Algorithm&#8217;''</p><p>Choose the algorithms you want to use for the message digest and for the signature itself. Both algorithms are required and must be compatible with the  selected key on the previous wizard page.</p><p>''&#8218;Properties&#8217;''</p><p>There is only one property available: Keep root element as plain text. This creates an encrypted XML document (fragment) with a root element in plain text. In case you selected to encrypt the whole document the documents root element will be kept as plain text. In case you selected to encrypt a document fragment only (via a text selection or an XPath expression) this will result in a plain text root element of this document fragment.</p><p>''&#8218;Signature ID&#8217;''</p><p>The signature ID is optional, but it is strongly required to enter one. This ID must be unique in the whole document and may not contain &lt;, >, &amp;, &#8218; or " characters. Without a signature ID it might get difficult to verify multiple signatures in one document and it is impossible to use &#8217;'&#8218;Quick Verification&#8217;''.</p><p>''&#8218;Encryption Wizard&#8217;''</p><p>Select the checkbox in case you want to start the [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html | XML Encryption Wizard]] directly after the signature process was successfully finished.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html
deleted file mode 100644
index 254bd09..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Insert_a_new_Key_in_an_existing_Keystore">Insert a new Key in an existing Keystore</h1><p><b>Insert a new Key in an existing Keystore</b> is one of the alternatives as the second wizard page. Select an existing keystore (probably one you created before with the help of the <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html">Create a new Key and a new Keystore</a> wizard) and enter the keystore password. After that simply select the desired algorithm and the algorithm size for the new key and enter a name and a password for it. Click the <b>Generate</b> button when you are done to create the new key. A short message informs you about the generation result and the <b>Next</b> button will be enabled. The key generated here will be used in the active signature process.</p><p><img align="middle" title="Insert a new Key in an existing Keystore" alt="Insert a new Key in an existing Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2b.png‎"/></p><p>Keys must be unique inside a keystore, so the wizard verifies that the entered key name does not exist in the selected keystore.</p><p>The wizard automatically stores the entered data for the keystore path and name between sessions. Passwords are never stored and have to be entered every time.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html
deleted file mode 100644
index dc107c6..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Create_a_new_Key_and_a_new_Keystore">Create a new Key and a new Keystore</h1><p><b>Create a new Key and a new Keystore</b> is one of the alternatives as the second wizard page. This page lets you create a new keystore together with a new key. Enter the name for the keystore and the password to protect it. After that choose an algorithm and its size and enter an alias name together with a password for the key. The keystore password is used to protect the whole keystore, the key password to protect the key. Both passwords are required.</p><p>Click the <b>Generate</b> button when you are done to create the new keystore together with the key. A short message informs you about the generation result and the <b>Next</b> button will be enabled. The keystore is stored with the entered name in the active folder (normally the active project). The key generated here will be used in the active signature process.</p><p><img align="middle" title="Create a new Key and a new Keystore" alt="Create a new Key and a new Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2c.png‎"/></p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_keys.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_keys.html
deleted file mode 100644
index 46077ab..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_keys.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Keystores_and_Keys">Keystores and Keys</h1><p>The second page of the <b>XML Signature Wizard</b> depends on your <b>Keystore and Key</b> selection on the first wizard page. You can select to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html">Use a Key from an existing Keystore</a>, <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html">Insert a new Key in an existing Keystore</a> or to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html">Create a new Key and a new Keystore</a>.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html
deleted file mode 100644
index ea42f33..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Use_a_Key_from_an_existing_Keystore">Use a Key from an existing Keystore</h1><p><b>Use a Key from an existing Keystore</b> is one of the alternatives as the second wizard page. Simply select the keystore containing the key you want to use in the current signature process. All data is verified, you can only switch to the next case with a correct keystore and key password as well as an existing key alias.</p><p><img align="middle" title="Use a Key from an existing Keystore" alt="Use a Key from an existing Keystore" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2a.png‎"/></p><p>The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_resource.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_resource.html
deleted file mode 100644
index 72e914e..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/page_resource.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Resource_and_Signature_Type">Resource and Signature Type</h1><p>This is the first page of the XML Signature Wizard. You'll have to select the resource you want to sign, the signature type, the keystore/ key option and the Basic Security Profile option.</p><p><img align="middle" title="Resource and Signature Type" alt="Resource and Signature Type" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_1.png‎"/></p><p><b>Resource</b></p><p>It is possible to sign the complete document, the selected text or a document fragment specified by an XPath expression. The complete document is always possible. For a text selection this selection has to exist before launching the wizard and it has to be well-formed. XPath is always possible too. You can either enter an XPath expression in the textfield or you can select one in the dialog after clicking on the <b>Browse...</b> button. The XPath expression has to return exactly one element or element content. Signing attributes is not supported.</p><p><b>Signature Type</b></p><p>There are three different signature types available. The difference between them is the position of the signed data and the signature itself.An <i>enveloped</i> and an <i>enveloping</i> signature are relatively equal. Both types to store the signed data (and possibly some unsigned data as well) together with the signature in the same XML document. With the <b>XML Security Tools</b> the signature will be placed in the XML document you have chosen to sign.So, the difference between an enveloped and an enveloping signature is, that with an enveloping signature the signed content is moved inside the XML signature element (into an <i>object</i> element). With an enveloped signature, the signature is a child element of the signed data. A detached signature may be something completely different. The normal detached signature consists of two documents: one containing the signature and one containing the signed data. To make it more complicated you can create a detached signature within one document too (but not with the <b>XML Security Tools</b>). With the XML Signature Wizard you do have to select a file to sign when selecting to create a detached signature.</p><p>Confused about all the possibilities? Well, there are quite some, and the differences are not often that clear. Simply give it a try and sign your XML documents with the different signature types.</p><p><b>Keystore and Key</b></p><p>The chosen option here sets the following wizard page. You can either select to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html">Use a key from an existing keystore</a>, to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html">Insert a new key in an existing keystore</a> or to <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html">Create a new key and a new keystore</a>.</p><p><b>Basic Security Profile</b></p><p>A Basic Security Profile compliant XML Signature has some restrictions in comparison to a regular XML Signature. By activating this checkbox all options in the XML Signature Wizard will be limited to options that are compliant to this profile. In case of the XML Signature Wizard this only limits the available algorithms on the <a href="/help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html" title="help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html">Algorithms and Signature Properties</a> page.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/sign.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/sign.html
deleted file mode 100644
index 667b737..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/signature/sign.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="XML_Signature_Wizard">XML Signature Wizard</h1><p>The <b>XML Signature Wizard</b> consists of three pages, with a variable second page depending on the chosen keystore/ key option. To launch the wizard you either have to select an XML document in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose <b>XML Security</b> and click on <b>New Signature...</b>. In order to sign a selected XML fragment select the desired document part in the editor and launch the wizard as described before. The selection has to exist before launching the wizard, and it has to be well-formed: in case a start-tag is selected the end-tag must be selected too. Signing only text-content of an element is possible too.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/verification/verify.html b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/verification/verify.html
deleted file mode 100644
index 1a9913b..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/html/verification/verify.html
+++ /dev/null
@@ -1 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?><!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"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="XML_Signatures_View">XML Signatures View</h1><p>The <b>XML Signatures</b> view lists all signatures contained in the selected XML document, together with their status (valid, invalid, unknown) and some additional signature information.You can either open this view manually by selecting <b>Window --> Show View --> Other --> XML --> XML Signatures</b> or you can use the <b>XML Security</b> context menu and select <b>New Verification...</b> which opens the view automatically.</p><p><img align="middle" title="XML Signatures view" alt="XML Signatures view" border="0" src="PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/verify/view.png‎"/></p><p>The toolbar (and the menu as well as the context menu) enable you to refresh all signatures for the currently opened (active) XML document. This scans the document and shows you all discovered signatures, as well as their status and some other information. This is a shortcut which enables you to find signatures in another XML document without using the context menu in the editor or view again.</p><p>The signature properties are accessible via the toolbar icon or by double clicking on a view entry. This will open a dialog with additional information on the selected entry.</p><h2 id="Unknown_Signatures">Unknown Signatures</h2><p>Sometimes verification of a signature fails.This may happen when required XML elements or attributes are missing or the XML document is itself invalid. For security reasons, you should regard an unknown signature status as an invalid signature. Depending on the missing parts it may even be possible that the signature details dialog (<i>Properties</i>) cannot be opened because too much required information is missing.</p></body></html>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.properties b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.properties
deleted file mode 100644
index 399f631..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.properties
+++ /dev/null
@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2009 Dominik Schadow - http://www.xml-sicherheit.de
-# 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:
-#     Dominik Schadow - initial API and implementation
-###############################################################################
-bundleName=XML Security Tools Doc (Incubating)
-bundleProvider=Eclipse.org
-decryptionCheatSheet=XML Decryption
-decryptionCheatSheetDescription=This tutorial shows you how to decrypt an XML document.
-signatureCheatSheet=XML Signature
-signatureCheatSheetDescription=This tutorial shows you how to sign an XML document.
-encryptionCheatSheet=XML Encryption
-encryptionCheatSheetDescription=This tutorial shows you how to encrypt an XML document.
-verificationCheatSheet=XML Verification
-verificationCheatSheetDescription=This tutorial shows you how to verify an XML Signature.
-xmlSecurityCheatSheet=XML Security
-quickFunctionsCheatSheet=XML Quick...
-quickFunctionsCheatSheetDescription=This tutorial shows you how to use the different Quick Functions of the XML Security Tools.
-extension.name = org.eclipse.wst.xml.security.doc.context
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.xml
deleted file mode 100644
index 2e52f90..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/plugin.xml
+++ /dev/null
@@ -1,71 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<?eclipse version="3.2"?>

-<plugin>

-   <!-- Help Topics -->

-   <extension

-         point="org.eclipse.help.toc">

-      <toc

-            file="toc.xml"

-            primary="true">

-      </toc>      

-   </extension>

-   <!-- Context Help -->

-   <extension

-         id="org.eclipse.wst.xml.security.doc.context"

-         name="%extension.name"

-         point="org.eclipse.help.contexts">

-      <contexts file="contexts.xml"/>

-   </extension>

-   <extension

-         point="org.eclipse.ui.cheatsheets.cheatSheetContent">

-      <category

-            id="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            name="%xmlSecurityCheatSheet">

-      </category>

-      <cheatsheet

-            category="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            contentFile="cheatsheets/sign.xml"

-            id="org.eclipse.wst.xml.security.core.cheatsheets.sign"

-            name="%signatureCheatSheet">

-         <description>

-            %signatureCheatSheetDescription

-         </description>

-      </cheatsheet>

-      <cheatsheet

-            category="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            contentFile="cheatsheets/verify.xml"

-            id="org.eclipse.wst.xml.security.core.cheatsheets.verify"

-            name="%verificationCheatSheet">

-         <description>

-            %verificationCheatSheetDescription

-         </description>

-      </cheatsheet>

-      <cheatsheet

-            category="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            contentFile="cheatsheets/encrypt.xml"

-            id="org.eclipse.wst.xml.security.core.cheatsheets.encrypt"

-            name="%encryptionCheatSheet">

-         <description>

-            %encryptionCheatSheetDescription

-         </description>

-      </cheatsheet>

-      <cheatsheet

-            category="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            contentFile="cheatsheets/decrypt.xml"

-            id="org.eclipse.wst.xml.security.core.cheatsheets.decrypt"

-            name="%decryptionCheatSheet">

-         <description>

-            %decryptionCheatSheetDescription

-         </description>

-      </cheatsheet>

-      <cheatsheet

-            category="org.eclipse.wst.xml.security.core.cheatsheets.category"

-            contentFile="cheatsheets/quick.xml"

-            id="org.eclipse.wst.xml.security.core.cheatsheets.quick"

-            name="%quickFunctionsCheatSheet">

-         <description>

-            %quickFunctionsCheatSheetDescription

-         </description>

-      </cheatsheet>

-   </extension>

-</plugin>

diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/pom.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/pom.xml
deleted file mode 100644
index 6b2d9a2..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/pom.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
-	<modelVersion>4.0.0</modelVersion>
-
-	<parent>
-		<groupId>org.eclipse.wst.xml.security</groupId>
-		<artifactId>org.eclipse.wst.xml.security-parent</artifactId>
-		<version>0.5.0-SNAPSHOT</version>
-		<relativePath>../../development/org.eclipse.wst.xml.security.releng</relativePath>
-	</parent>
-
-	<artifactId>org.eclipse.wst.xml.security.doc</artifactId>
-	<version>0.5.0-SNAPSHOT</version>
-	<packaging>eclipse-plugin</packaging>
-	<name>XML Security: User Documentation</name>
-</project>
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/toc.xml b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/toc.xml
deleted file mode 100644
index 3b25651..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/toc.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="XML Security Tools User Guide" topic="html/contents.html">
-   <topic href="html/overview/overview.html" label="Overview">
-   </topic>
-   <topic href="html/overview/tasks.html" label="Tasks">
-		<topic label="Signature Wizard" href="html/signature/sign.html">
-	        <topic label="Resource and Signature Type" href="html/signature/page_resource.html"/>
-	        <topic label="Keystores and Keys" href="html/signature/page_keys.html">
-	            <topic label="Use a Key from an existing Keystore" href="html/signature/page_open_key.html"/>
-	            <topic label="Insert a new Key in an existing Keystore" href="html/signature/page_create_key.html"/>
-	            <topic label="Create a new Key and a new Keystore" href="html/signature/page_create_keystore.html"/>
-	        </topic>
-	        <topic label="Algorithms and Signature Properties" href="html/signature/page_algorithms.html"/>
-	    </topic>
-	    <topic label="Signatures View" href="html/verification/verify.html"/>
-	    <topic label="Encryption Wizard" href="html/encryption/encrypt.html">
-	        <topic label="Resource and Encryption Type" href="html/encryption/page_resource.html"/>
-	        <topic label="Keystores and Keys" href="html/encryption/page_keys.html">
-	            <topic label="Use a Key from an existing Keystore" href="html/encryption/page_open_key.html"/>
-	            <topic label="Insert a new Key in an existing Keystore" href="html/encryption/page_create_key.html"/>
-	            <topic label="Create a new Key and a new Keystore" href="html/encryption/page_create_keystore.html"/>
-	        </topic>
-	        <topic label="Algorithms and Encryption Properties" href="html/encryption/page_algorithms.html"/>
-	    </topic>
-	    <topic label="Decryption Wizard" href="html/decryption/decrypt.html">
-	        <topic label="Resource and Decryption Type" href="html/decryption/page_resource.html"/>
-         <topic href="html/decryption/page_open_a_key.html" label="Open a Key">
-         </topic>
-	    </topic>
-	    <topic label="Canonicalization" href="html/canonicalization/canonicalize.html"/>
-	    <topic label="Quick Functions" href="html/quickfunctions/quickfunctions.html"/>
-	</topic>
-    <topic label="Preferences" href="html/preferences/general.html">
-        <topic label="Encryption" href="html/preferences/encryption.html"/>
-        <topic label="Signature" href="html/preferences/signature.html"/>
-    </topic>
-    <topic href="html/legal.html" label="Notices">
-    </topic>
-</toc>
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/canonicalization/canonicalize.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/canonicalization/canonicalize.textile
deleted file mode 100644
index ed90b92..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/canonicalization/canonicalize.textile
+++ /dev/null
@@ -1,5 +0,0 @@
-= XML Canonicalization =
-
-XML Canonicalization does not open any wizard or view. Instead, it directly canonicalizes (normalizes) the selected XML document (always the complete document). Depending on the selected menu entry it either maintains the comments or removes them. Removed comments are replaced by an empty line. The '''XML Security''' [[help/topic/org.eclipse.wst.xml.security.doc/html/preferences/general.html | preferences]] allow you to switch between ''inclusive'' and ''exclusive'' XML canonicalization, which may result into different canonicalized versions of the XML document (the differences depend on the XML document).
-
-'''XML Canonicalization''' always takes place when signing an XML document or verifying an XML Signature. There is no need to execute this task manually (but it does not do any damage in case you do).
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/contents.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/contents.textile
deleted file mode 100644
index 88705dd..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/contents.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= XML Security Tools User Guide =
-
-This guide provides instructions and information on how to use the '''XML Security Tools'''.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/decrypt.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/decrypt.textile
deleted file mode 100644
index a8e5a56..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/decrypt.textile
+++ /dev/null
@@ -1,5 +0,0 @@
-= XML Decryption Wizard =
-
-The '''XML Decryption Wizard''' consists of two pages: [[help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_resource.html | Resource and Decryption Type]] and [[help/topic/org.eclipse.wst.xml.security.doc/html/decryption/page_open_a_key.html | Open a key]].
-
-To launch the wizard you either have to select an encrypted XML document  in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose '''XML Security''' and click on '''New Decryption...'''.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_open_a_key.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_open_a_key.textile
deleted file mode 100644
index f7e15fb..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_open_a_key.textile
+++ /dev/null
@@ -1,11 +0,0 @@
-= Open a key =
-
-This is the second page of the XML Decryption Wizard. You'll have to provide the keystore and key information used to encrypt the XML document (-fragment).
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_2.png‎|Open a key|center]]
-
-'''Keystore and Key'''
-
-Simply choose the keystore containing the used key and enter the keystore password. Type in the key name and its password.
-
-The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_resource.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_resource.textile
deleted file mode 100644
index a4513aa..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/decryption/page_resource.textile
+++ /dev/null
@@ -1,9 +0,0 @@
-= Resource =
-
-This is the first page of the XML Decryption Wizard. You'll have to choose the encryption you want to decrypt.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/decrypt/page_1.png‎|Resource and decryption type|center]]
-
-'''Encryption ID'''
-
-An XML document can contain multiple encryptions with different encryption IDs. You do not have to decrypt them in document order. Instead, you can choose which one you want to decrypt (make sure to provide the corresponding keystore and key information, otherwise decryption will fail). However, this requires an ID for the XML encryption. Since IDs are optional you can choose to decrypt the first encrypted part in the XML document instead. In case the XML document contains multiple encryptions without IDs you'll have to decrypt them step by step. In order to avoid that always provide encryption IDs when encrypting XML data.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/encrypt.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/encrypt.textile
deleted file mode 100644
index d2b2cab..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/encrypt.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= XML Encryption Wizard =
-
-The '''XML Encryption Wizard''' consists of three pages, with a variable second page depending on the chosen keystore/ key option. To launch the wizard you either have to select an XML document in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose '''XML Security''' and click on '''New Encryption...'''. In order to encrypt a selected XML fragment select the desired document part in the editor and launch the wizard as described before. The selection has to exist before launching the wizard, and it has to be well-formed: in case a start-tag is selected the end-tag must be selected too. Encrypting only text-content of an element is possible too.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_algorithms.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_algorithms.textile
deleted file mode 100644
index ba4d526..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_algorithms.textile
+++ /dev/null
@@ -1,21 +0,0 @@
-= Algorithms and Encryption Properties =
-
-This is the last page of the XML Encryption Wizard. You must select the Encryption and the Key Wrap Algorithms. Optional, you can select to keep the root element as plain text and you can enter an encryption ID (strongly recommended). The '''Start Signature Wizard afterwards''' checkbox enables you to start the signature wizard after successfully encrypting the selected XML document.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_3.png‎|Algorithms and Encryption Properties|center]]
-
-'''Encryption and Key Wrap Algorithm'''
-
-Choose the algorithms you want to use to encrypt the XML document (fragment) and to wrap the key. You have to select algorithms that do match with the selected key on the previous wizard page.
-
-'''Properties'''
-
-There is only one property available: Keep root element as plain text. This creates an encrypted XML document (fragment) with a root element in plain text. In case you selected to encrypt the whole document the documents root element will be kept as plain text. In case you selected to encrypt a document fragment only (via a text selection or an XPath expression) this will result in a plain text root element of this document fragment.
-
-'''Encryption ID'''
-
-The encryption ID is optional, but it is strongly required to enter one. This ID must be unique in the whole document and may not contain <, >, &, ' or " characters. Without an encryption ID it is only possible to decrypt the XML document step by step.
-
-'''Signature Wizard'''
-
-Select the checkbox in case you want to start the [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html | XML Signature Wizard]] directly after the encryption process was successfully finished.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_key.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_key.textile
deleted file mode 100644
index 96bb6f0..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_key.textile
+++ /dev/null
@@ -1,9 +0,0 @@
-= Insert a new Key in an existing Keystore =
-
-'''Insert a new Key in an existing Keystore''' is one of the alternatives as the second wizard page. Select an existing keystore (probably one you created before with the help of the [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html | Create a new Key and a new Keystore]] wizard) and enter the keystore password. After that simply select the desired algorithm and the algorithm size for the new key and enter a name and a password for it. Click the '''Generate''' button when you are done to create the new key. A short message informs you about the generation result and the '''Next''' button will be enabled. The key generated here will be used in the active encryption process.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2b.png‎|Insert a new Key in an existing Keystore|center]]
-
-Keys must be unique inside a keystore, so the wizard verifies that the entered key name does not exist in the selected keystore.
-
-The wizard automatically stores the entered data for the keystore path and name between sessions. Passwords are never stored and have to be entered every time.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_keystore.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_keystore.textile
deleted file mode 100644
index b4a4948..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_create_keystore.textile
+++ /dev/null
@@ -1,7 +0,0 @@
-= Create a new Key and a new Keystore =
-
-'''Create a new Key and a new Keystore''' is one of the alternatives as the second wizard page. This page lets you create a new keystore together with a new key. Enter the name for the keystore and the password to protect it. After that choose an algorithm and its size and enter an alias name together with a password for the key. The keystore password is used to protect the whole keystore, the key password to protect the key. Both passwords are required.
-
-Click the '''Generate''' button when you are done to create the new keystore together with the key. A short message informs you about the generation result and the '''Next''' button will be enabled. The keystore is stored with the entered name in the active folder (normally the active project). The key generated here will be used in the active encryption process.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2c.png‎|Create a new Key and a new Keystore|center]]
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_keys.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_keys.textile
deleted file mode 100644
index fa25f87..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_keys.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= Keystores and Keys =
-
-The second page of the '''XML Encryption Wizard''' depends on your '''Keystore and Key''' selection on the first wizard page. You can select to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html | Use a Key from an existing Keystore]], [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html | Insert a new Key in an existing Keystore]] or to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html | Create a new Key and a new Keystore]].
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_open_key.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_open_key.textile
deleted file mode 100644
index 4aba039..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_open_key.textile
+++ /dev/null
@@ -1,7 +0,0 @@
-= Use a Key from an existing Keystore =
-
-'''Use a Key from an existing Keystore''' is one of the alternatives as the second wizard page. Simply select the keystore containing the key you want to use in the current encryption process. All data is verified, you can only switch to the next case with a correct keystore and key password as well as an existing key alias.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_2a.png‎|Use a Key from an existing Keystore|center]]
-
-The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_resource.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_resource.textile
deleted file mode 100644
index 7458626..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/encryption/page_resource.textile
+++ /dev/null
@@ -1,21 +0,0 @@
-= Resource and Encryption Type =
-
-This is the first page of the XML Encryption Wizard. You'll have to select the resource you want to encrypt, the encryption type, the keystore/ key option and the Basic Security Profile option.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/encrypt/page_1.png‎|Resource and Encryption Type|center]]
-
-'''Resource'''
-
-It is possible to encrypt the complete document, the selected text or a document fragment specified by an XPath expression. The complete document is always possible. For a text selection this selection has to exist before launching the wizard and it has to be well-formed. XPath is always possible too. You can either enter an XPath expression in the textfield or you can select one in the dialog after clicking on the '''Browse...''' button. The XPath expression has to return exactly one element or element content. Encrypting attributes is not supported.
-
-'''Encryption Type'''
-
-The normal encryption type is a so called enveloping encryption, where the encrypted data is contained in the original document (it replaces the plain XML). A detached encryption doesn't encrypt the XML document you have chosen. Instead the data in the specified additional file here gets encrypted. Both documents will be changed. File A remains in plain XML, but does contain the encryption information for file B that gets encrypted (a detached encryption requires the whole document to be encrypted).
-
-'''Keystore and Key'''
-
-The chosen option here sets the following wizard page. You can either select to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_open_key.html | Use a key from an existing keystore]], to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_key.html | Insert a new key in an existing keystore]] or to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_create_keystore.html | Create a new key and a new keystore]].
-
-'''Basic Security Profile'''
-
-A Basic Security Profile compliant XML Encryption has some restrictions in comparison to a regular XML Encryption. By activating this checkbox all options in the XML Encryption Wizard will be limited to options that are compliant to this profile. In case of the XML Encryption Wizard this only limits the available algorithms on the [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/page_algorithms.html | Algorithms and Encryption Properties]] page.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/overview.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/overview.textile
deleted file mode 100644
index de1c64e..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/overview.textile
+++ /dev/null
@@ -1,27 +0,0 @@
-= Overview =
-
-'''XML Security Tools''' add three wizards for [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html | signing]], [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html | encrypting]] and [[help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html | decrypting]] various XML documents to the WTP XML editor and different views. A new view, XML Signatures, is included for [[help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html | verification]] of all XML signatures in the selected XML document as well as to provide detailed information on each signature.
-
-== Launching XML Security Tools ==
-
-To call any functionality of the XML Security Tools simply select an XML document in the ''Navigator'', ''Package Explorer'' or ''Project Explorer'' view or inside the WTP XML editor and choose the desired operation in the '''XML Security''' entry in the context menu. The XML Security context menu inside the mentioned views is only available in the ''XML perspective''. It is always available inside the WTP XML editor, no matter which perspective is active at the moment.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/overview/context_menu.png‎|XML Security Tools context menu|center]]
-
-== The XML Security menu ==
-
-The XML Security menu contains ten entries. The items with an icon launch a wizard ('''New Signature...''', '''New Encryption...''', '''New Decryption...''') or a view ('''New Verification...'''). The ones without any icon launch a command directly, with minimum or no user interaction at all.
-
-There are no differences in the menu when calling it from inside the XML editor on inside a view. However there is one difference in the '''XML Signature''' and '''XML Encryption''' wizard: it is not possible to sign/ encrypt a text selection when using the context menu inside a view. The text selection has to exist before opening the wizard, which is not possible from within a view.
-
-Calling any XML Security command from within the XML editor activates the Eclipse undo/ redo functionality. Keep that in mind since it makes it easy to undo any encryption while the editor is still open. Calling any XML Security command from within a view writes any changes directly to the selected file, without any undo/ redo possibility.
-
-== Quick Functionality ==
-
-The so called ''Quick Functions'' - '''Quick Signature''', '''Quick Verification''', '''Quick Encryption''' and '''Quick Decryption''' - require less or no user interaction at all. These commands use predefined preferences and only ask the user for security sensitive information like passwords. This is the fastest way to sign, verify, encrypt or decrypt any XML document. A dialog opens in case there are any missing preferences to continue the operation. You can either jump directly to the corresponding preference page and provide the information (like the keystore to use, the desired algorithm, signature id and so on) or cancel the complete operation.
-
-It is possible to mix ''normal'' XML Security operations with the quick functions. So you can encrypt an XML document with the wizard and decrypt it using the '''Quick Decryption''' function. The only requirement is that the settings you have chosen in the wizard do match the preference settings for XML Decryption.
-
-== XML Security Preferences ==
-
-The '''XML Security''' preferences are available as sub-pages in the '''XML''' category. Three pages are available, from general settings on the '''XML Security''' page to specific settings for '''Encryption''' and '''Signatures'''. It is wise to define different IDs for signature and encryption, this makes verification and decryption much easier. Quick Verification and Quick Decryption may fail in case the IDs are not unique.
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/tasks.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/tasks.textile
deleted file mode 100644
index 9a23302..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/overview/tasks.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= Tasks =
-
-The '''XML Security Tools''' enable you to [[help/topic/org.eclipse.wst.xml.security.doc/html/canonicalization/canonicalize.html | canonicalize]], [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/sign.html | sign]], [[help/topic/org.eclipse.wst.xml.security.doc/html/verification/verify.html | verify]] and to [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html | encrypt]] and [[help/topic/org.eclipse.wst.xml.security.doc/html/decryption/decrypt.html | decrypt]] arbitrary XML documents in your Eclipse workbench.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/encryption.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/encryption.textile
deleted file mode 100644
index fe19ae7..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/encryption.textile
+++ /dev/null
@@ -1,5 +0,0 @@
-= Encryption Preferences =
-
-All settings on this page only affect '''Quick Encryption''' and '''Quick Decryption''', not the normal wizards. Here you can select what you want to encrypt - the whole document, a selection or a document fragment identified by an XPath expression. The encryption type is fixed to ''Enveloping'' at the moment. Select the algorithms to use and provide a keystore containing a key which match those algorithms. Chose the encryption id carefully. Quick Decryption searches for this id, so it should be unique.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/encryption.png‎|XML Security Tools encryption preferences|center]]
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/general.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/general.textile
deleted file mode 100644
index f647817..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/general.textile
+++ /dev/null
@@ -1,9 +0,0 @@
-= General Preferences =
-
-The '''XML Security''' preferences are available as sub-pages in the '''XML''' category. Three pages are available, from general settings on the '''XML Security''' page to specific settings for [[help/topic/org.eclipse.wst.xml.security.doc/html/preferences/encryption.html | Encryption]] and [[help/topic/org.eclipse.wst.xml.security.doc/html/preferences/signature.html | Signatures]].
-
-The general XML Security Tools preference page allows you to specify some general settings for the whole plug-in.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/general.png‎|XML Security Tools preferences|center]]
-
-By default, an exclusive XML canonicalization is executed when selecting on of the Canonicalization entries in the menu. Select the inclusive option in case you do require this canonicalization type. The canonicalization target is normally the same file, so the original file gets manipulated. In case you do want to keep the original file you can select to create a new document for canonicalization. This only affects canonicalization, not any of the other wizards! Creating a new file adds _canon to the filename, with additional numbering in case this file already exists.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/signature.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/signature.textile
deleted file mode 100644
index 2a007ef..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/preferences/signature.textile
+++ /dev/null
@@ -1,5 +0,0 @@
-= Signature Preferences =
-
-All settings on this page only affect '''Quick Signature''' and '''Quick Verification''', not the normal wizard or view. Here you can select what you want to sign - the whole document, a selection or a document fragment identified by an XPath expression. The signature types ''Enveloping'' and ''Enveloped'' are available. Select the different algorithms to use and provide a keystore containing a key which match those algorithms. Chose the signature id carefully. Quick Verification searches for this id, so it should be unique.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/preferences/signature.png‎|XML Security Tools signature preferences|center]]
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/quickfunctions/quickfunctions.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/quickfunctions/quickfunctions.textile
deleted file mode 100644
index cf28228..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/quickfunctions/quickfunctions.textile
+++ /dev/null
@@ -1,5 +0,0 @@
-= Quick Functions =
-
-The so called ''Quick Functions'' - '''Quick Signature''', '''Quick Verification''', '''Quick Encryption''' and '''Quick Decryption''' - require less or no user interaction at all. These commands use predefined preferences and only ask the user for security sensitive information like passwords. This is the fastest way to sign, verify, encrypt or decrypt any XML document. A dialog opens in case there are any missing [[help/topic/org.eclipse.wst.xml.security.doc/html/preferences/general.html | preferences]] to continue the operation. You can either jump directly to the corresponding preference page and provide the information (like the keystore to use, the desired algorithm, signature id and so on) or cancel the complete operation.
-
-It is possible to mix ''normal'' XML Security operations with the quick functions. So you can encrypt an XML document with the wizard and decrypt it using the '''Quick Decryption''' function. The only requirement is that the settings you have chosen in the wizard do match the preference settings for XML Decryption.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_algorithms.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_algorithms.textile
deleted file mode 100644
index c7bdf01..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_algorithms.textile
+++ /dev/null
@@ -1,25 +0,0 @@
-= Algorithms and Signature Properties =
-
-This is the last page of the XML Signature Wizard. You must select algorithms for the message digest and the signature as well as a canonicalization and transformation algorithm. Optional, you can define some signature properties and you can enter a signature ID (strongly recommended). The '''Start Encryption Wizard afterwards''' checkbox enables you to start the encryption wizard after successfully signing the selected XML document.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_3.png‎|Algorithms and Signature Properties|center]]
-
-'''Canonicalization and Transformation Algorithm'''
-
-Choose the algorithms you want to use for canonicalization and transformation. Whereas canonicalization is required, the transformation algorithm can be set to ''none''.
-
-'''Message Digest and Signature Algorithm'''
-
-Choose the algorithms you want to use for the message digest and for the signature itself. Both algorithms are required and must be compatible with the  selected key on the previous wizard page.
-
-'''Properties'''
-
-There is only one property available: Keep root element as plain text. This creates an encrypted XML document (fragment) with a root element in plain text. In case you selected to encrypt the whole document the documents root element will be kept as plain text. In case you selected to encrypt a document fragment only (via a text selection or an XPath expression) this will result in a plain text root element of this document fragment.
-
-'''Signature ID'''
-
-The signature ID is optional, but it is strongly required to enter one. This ID must be unique in the whole document and may not contain <, >, &, ' or " characters. Without a signature ID it might get difficult to verify multiple signatures in one document and it is impossible to use '''Quick Verification'''.
-
-'''Encryption Wizard'''
-
-Select the checkbox in case you want to start the [[help/topic/org.eclipse.wst.xml.security.doc/html/encryption/encrypt.html | XML Encryption Wizard]] directly after the signature process was successfully finished.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_key.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_key.textile
deleted file mode 100644
index 78a62e4..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_key.textile
+++ /dev/null
@@ -1,9 +0,0 @@
-= Insert a new Key in an existing Keystore =
-
-'''Insert a new Key in an existing Keystore''' is one of the alternatives as the second wizard page. Select an existing keystore (probably one you created before with the help of the [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html | Create a new Key and a new Keystore]] wizard) and enter the keystore password. After that simply select the desired algorithm and the algorithm size for the new key and enter a name and a password for it. Click the '''Generate''' button when you are done to create the new key. A short message informs you about the generation result and the '''Next''' button will be enabled. The key generated here will be used in the active signature process.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2b.png‎|Insert a new Key in an existing Keystore|center]]
-
-Keys must be unique inside a keystore, so the wizard verifies that the entered key name does not exist in the selected keystore.
-
-The wizard automatically stores the entered data for the keystore path and name between sessions. Passwords are never stored and have to be entered every time.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_keystore.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_keystore.textile
deleted file mode 100644
index 1cadd96..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_create_keystore.textile
+++ /dev/null
@@ -1,7 +0,0 @@
-= Create a new Key and a new Keystore =
-
-'''Create a new Key and a new Keystore''' is one of the alternatives as the second wizard page. This page lets you create a new keystore together with a new key. Enter the name for the keystore and the password to protect it. After that choose an algorithm and its size and enter an alias name together with a password for the key. The keystore password is used to protect the whole keystore, the key password to protect the key. Both passwords are required.
-
-Click the '''Generate''' button when you are done to create the new keystore together with the key. A short message informs you about the generation result and the '''Next''' button will be enabled. The keystore is stored with the entered name in the active folder (normally the active project). The key generated here will be used in the active signature process.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2c.png‎|Create a new Key and a new Keystore|center]]
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_keys.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_keys.textile
deleted file mode 100644
index ac926c2..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_keys.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= Keystores and Keys =
-
-The second page of the '''XML Signature Wizard''' depends on your '''Keystore and Key''' selection on the first wizard page. You can select to [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html | Use a Key from an existing Keystore]], [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html | Insert a new Key in an existing Keystore]] or to [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html | Create a new Key and a new Keystore]].
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_open_key.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_open_key.textile
deleted file mode 100644
index dedfe44..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_open_key.textile
+++ /dev/null
@@ -1,7 +0,0 @@
-= Use a Key from an existing Keystore =
-
-'''Use a Key from an existing Keystore''' is one of the alternatives as the second wizard page. Simply select the keystore containing the key you want to use in the current signature process. All data is verified, you can only switch to the next case with a correct keystore and key password as well as an existing key alias.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_2a.png‎|Use a Key from an existing Keystore|center]]
-
-The wizard automatically stores the entered data for the keystore name and the key name between sessions. Passwords are never stored and have to be entered every time.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_resource.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_resource.textile
deleted file mode 100644
index 8d53546..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/page_resource.textile
+++ /dev/null
@@ -1,23 +0,0 @@
-= Resource and Signature Type =
-
-This is the first page of the XML Signature Wizard. You'll have to select the resource you want to sign, the signature type, the keystore/ key option and the Basic Security Profile option.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/sign/page_1.png‎|Resource and Signature Type|center]]
-
-'''Resource'''
-
-It is possible to sign the complete document, the selected text or a document fragment specified by an XPath expression. The complete document is always possible. For a text selection this selection has to exist before launching the wizard and it has to be well-formed. XPath is always possible too. You can either enter an XPath expression in the textfield or you can select one in the dialog after clicking on the '''Browse...''' button. The XPath expression has to return exactly one element or element content. Signing attributes is not supported.
-
-'''Signature Type'''
-
-There are three different signature types available. The difference between them is the position of the signed data and the signature itself.An ''enveloped'' and an ''enveloping'' signature are relatively equal. Both types to store the signed data (and possibly some unsigned data as well) together with the signature in the same XML document. With the '''XML Security Tools''' the signature will be placed in the XML document you have chosen to sign.So, the difference between an enveloped and an enveloping signature is, that with an enveloping signature the signed content is moved inside the XML signature element (into an ''object'' element). With an enveloped signature, the signature is a child element of the signed data. A detached signature may be something completely different. The normal detached signature consists of two documents: one containing the signature and one containing the signed data. To make it more complicated you can create a detached signature within one document too (but not with the '''XML Security Tools'''). With the XML Signature Wizard you do have to select a file to sign when selecting to create a detached signature.
-
-Confused about all the possibilities? Well, there are quite some, and the differences are not often that clear. Simply give it a try and sign your XML documents with the different signature types.
-
-'''Keystore and Key'''
-
-The chosen option here sets the following wizard page. You can either select to [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_open_key.html | Use a key from an existing keystore]], to [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_key.html | Insert a new key in an existing keystore]] or to [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_create_keystore.html | Create a new key and a new keystore]].
-
-'''Basic Security Profile'''
-
-A Basic Security Profile compliant XML Signature has some restrictions in comparison to a regular XML Signature. By activating this checkbox all options in the XML Signature Wizard will be limited to options that are compliant to this profile. In case of the XML Signature Wizard this only limits the available algorithms on the [[help/topic/org.eclipse.wst.xml.security.doc/html/signature/page_algorithms.html | Algorithms and Signature Properties]] page.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/sign.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/sign.textile
deleted file mode 100644
index 64b1cef..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/signature/sign.textile
+++ /dev/null
@@ -1,3 +0,0 @@
-= XML Signature Wizard =
-
-The '''XML Signature Wizard''' consists of three pages, with a variable second page depending on the chosen keystore/ key option. To launch the wizard you either have to select an XML document in one of the supported views in the XML perspective or open an XML document in the WTP XML editor (in any perspective). Open the context menu, choose '''XML Security''' and click on '''New Signature...'''. In order to sign a selected XML fragment select the desired document part in the editor and launch the wizard as described before. The selection has to exist before launching the wizard, and it has to be well-formed: in case a start-tag is selected the end-tag must be selected too. Signing only text-content of an element is possible too.
\ No newline at end of file
diff --git a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/verification/verify.textile b/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/verification/verify.textile
deleted file mode 100644
index cd25da7..0000000
--- a/sourceediting/documentation/org.eclipse.wst.xml.security.doc/wiki/verification/verify.textile
+++ /dev/null
@@ -1,13 +0,0 @@
-= XML Signatures View =
-
-The '''XML Signatures''' view lists all signatures contained in the selected XML document, together with their status (valid, invalid, unknown) and some additional signature information.You can either open this view manually by selecting '''Window --> Show View --> Other --> XML --> XML Signatures''' or you can use the '''XML Security''' context menu and select '''New Verification...''' which opens the view automatically.
-
-[[Image:PLUGINS_ROOT/org.eclipse.wst.xml.security.doc/html/images/verify/view.png‎|XML Signatures view|center]]
-
-The toolbar (and the menu as well as the context menu) enable you to refresh all signatures for the currently opened (active) XML document. This scans the document and shows you all discovered signatures, as well as their status and some other information. This is a shortcut which enables you to find signatures in another XML document without using the context menu in the editor or view again.
-
-The signature properties are accessible via the toolbar icon or by double clicking on a view entry. This will open a dialog with additional information on the selected entry.
-
-== Unknown Signatures ==
-
-Sometimes verification of a signature fails.This may happen when required XML elements or attributes are missing or the XML document is itself invalid. For security reasons, you should regard an unknown signature status as an invalid signature. Depending on the missing parts it may even be possible that the signature details dialog (''Properties'') cannot be opened because too much required information is missing.
\ No newline at end of file
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/.project b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/.project
deleted file mode 100644
index f76e437..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/.project
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.wst.xml.security_sdk.feature</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.FeatureBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.FeatureNature</nature>
-	</natures>
-</projectDescription>
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/build.properties b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/build.properties
deleted file mode 100644
index c31e7f8..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/build.properties
+++ /dev/null
@@ -1,8 +0,0 @@
-bin.includes = feature.xml,\
-               eclipse_update_120.jpg,\
-               epl-v10.html,\
-               feature.properties,\
-               license.html
-               
-generate.feature@org.eclipse.wst.xml.security.feature.source=org.eclipse.wst.xml.security.feature
-               
\ No newline at end of file
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/eclipse_update_120.jpg b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/eclipse_update_120.jpg
deleted file mode 100644
index bfdf708..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/eclipse_update_120.jpg
+++ /dev/null
Binary files differ
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/epl-v10.html b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/epl-v10.html
deleted file mode 100644
index ed4b196..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/epl-v10.html
+++ /dev/null
@@ -1,328 +0,0 @@
-<html xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 9">
-<meta name=Originator content="Microsoft Word 9">
-<link rel=File-List
-href="./Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml">
-<title>Eclipse Public License - Version 1.0</title>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
-  <o:Revision>2</o:Revision>
-  <o:TotalTime>3</o:TotalTime>
-  <o:Created>2004-03-05T23:03:00Z</o:Created>
-  <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
-  <o:Pages>4</o:Pages>
-  <o:Words>1626</o:Words>
-  <o:Characters>9270</o:Characters>
-   <o:Lines>77</o:Lines>
-  <o:Paragraphs>18</o:Paragraphs>
-  <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
-  <o:Version>9.4402</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
-  <w:TrackRevisions/>
- </w:WordDocument>
-</xml><![endif]-->
-<style>
-<!--
- /* Font Definitions */
-@font-face
-	{font-family:Tahoma;
-	panose-1:2 11 6 4 3 5 4 4 2 4;
-	mso-font-charset:0;
-	mso-generic-font-family:swiss;
-	mso-font-pitch:variable;
-	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
- /* Style Definitions */
-p.MsoNormal, li.MsoNormal, div.MsoNormal
-	{mso-style-parent:"";
-	margin:0in;
-	margin-bottom:.0001pt;
-	mso-pagination:widow-orphan;
-	font-size:12.0pt;
-	font-family:"Times New Roman";
-	mso-fareast-font-family:"Times New Roman";}
-p
-	{margin-right:0in;
-	mso-margin-top-alt:auto;
-	mso-margin-bottom-alt:auto;
-	margin-left:0in;
-	mso-pagination:widow-orphan;
-	font-size:12.0pt;
-	font-family:"Times New Roman";
-	mso-fareast-font-family:"Times New Roman";}
-p.BalloonText, li.BalloonText, div.BalloonText
-	{mso-style-name:"Balloon Text";
-	margin:0in;
-	margin-bottom:.0001pt;
-	mso-pagination:widow-orphan;
-	font-size:8.0pt;
-	font-family:Tahoma;
-	mso-fareast-font-family:"Times New Roman";}
-@page Section1
-	{size:8.5in 11.0in;
-	margin:1.0in 1.25in 1.0in 1.25in;
-	mso-header-margin:.5in;
-	mso-footer-margin:.5in;
-	mso-paper-source:0;}
-div.Section1
-	{page:Section1;}
--->
-</style>
-</head>
-
-<body lang=EN-US style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<p align=center style='text-align:center'><b>Eclipse Public License - v 1.0</b>
-</p>
-
-<p><span style='font-size:10.0pt'>THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
-THE TERMS OF THIS ECLIPSE PUBLIC LICENSE (&quot;AGREEMENT&quot;). ANY USE,
-REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
-OF THIS AGREEMENT.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>1. DEFINITIONS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Contribution&quot; means:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and<br clear=left>
-b) in the case of each subsequent Contributor:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-changes to the Program, and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-additions to the Program;</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>where
-such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution 'originates' from a Contributor
-if it was added to the Program by such Contributor itself or anyone acting on
-such Contributor's behalf. Contributions do not include additions to the
-Program which: (i) are separate modules of software distributed in conjunction
-with the Program under their own license agreement, and (ii) are not derivative
-works of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>&quot;Contributor&quot; means any person or
-entity that distributes the Program.</span> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Licensed Patents &quot; mean patent
-claims licensable by a Contributor which are necessarily infringed by the use
-or sale of its Contribution alone or when combined with the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>&quot;Program&quot; means the Contributions
-distributed in accordance with this Agreement.</span> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Recipient&quot; means anyone who
-receives the Program under this Agreement, including all Contributors.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>2. GRANT OF RIGHTS</span></b> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-Subject to the terms of this Agreement, each Contributor hereby grants Recipient
-a non-exclusive, worldwide, royalty-free copyright license to<span
-style='color:red'> </span>reproduce, prepare derivative works of, publicly
-display, publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and object code
-form.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide,<span style='color:green'> </span>royalty-free
-patent license under Licensed Patents to make, use, sell, offer to sell, import
-and otherwise transfer the Contribution of such Contributor, if any, in source
-code and object code form. This patent license shall apply to the combination
-of the Contribution and the Program if, at the time the Contribution is added
-by the Contributor, such addition of the Contribution causes such combination
-to be covered by the Licensed Patents. The patent license shall not apply to
-any other combinations which include the Contribution. No hardware per se is
-licensed hereunder. </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>c)
-Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor
-that the Program does not infringe the patent or other intellectual property
-rights of any other entity. Each Contributor disclaims any liability to Recipient
-for claims brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the rights and
-licenses granted hereunder, each Recipient hereby assumes sole responsibility
-to secure any other intellectual property rights needed, if any. For example,
-if a third party patent license is required to allow Recipient to distribute
-the Program, it is Recipient's responsibility to acquire that license before
-distributing the Program.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>d)
-Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in
-this Agreement. </span></p>
-
-<p><b><span style='font-size:10.0pt'>3. REQUIREMENTS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>A Contributor may choose to distribute the
-Program in object code form under its own license agreement, provided that:</span>
-</p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it complies with the terms and conditions of this Agreement; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-its license agreement:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title
-and non-infringement, and implied warranties or conditions of merchantability
-and fitness for a particular purpose; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such
-as lost profits; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iii)
-states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iv)
-states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a
-medium customarily used for software exchange.<span style='color:blue'> </span></span></p>
-
-<p><span style='font-size:10.0pt'>When the Program is made available in source
-code form:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it must be made available under this Agreement; and </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b) a
-copy of this Agreement must be included with each copy of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Contributors may not remove or alter any
-copyright notices contained within the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Each Contributor must identify itself as the
-originator of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution. </span></p>
-
-<p><b><span style='font-size:10.0pt'>4. COMMERCIAL DISTRIBUTION</span></b> </p>
-
-<p><span style='font-size:10.0pt'>Commercial distributors of software may
-accept certain responsibilities with respect to end users, business partners
-and the like. While this license is intended to facilitate the commercial use
-of the Program, the Contributor who includes the Program in a commercial
-product offering should do so in a manner which does not create potential
-liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor (&quot;Commercial
-Contributor&quot;) hereby agrees to defend and indemnify every other
-Contributor (&quot;Indemnified Contributor&quot;) against any losses, damages and
-costs (collectively &quot;Losses&quot;) arising from claims, lawsuits and other
-legal actions brought by a third party against the Indemnified Contributor to
-the extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor
-to control, and cooperate with the Commercial Contributor in, the defense and
-any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.</span> </p>
-
-<p><span style='font-size:10.0pt'>For example, a Contributor might include the
-Program in a commercial product offering, Product X. That Contributor is then a
-Commercial Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance claims and
-warranties are such Commercial Contributor's responsibility alone. Under this
-section, the Commercial Contributor would have to defend claims against the
-other Contributors related to those performance claims and warranties, and if a
-court requires any other Contributor to pay any damages as a result, the
-Commercial Contributor must pay those damages.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>5. NO WARRANTY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, THE PROGRAM IS PROVIDED ON AN &quot;AS IS&quot; BASIS, WITHOUT
-WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
-WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
-MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and distributing the
-Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or
-equipment, and unavailability or interruption of operations. </span></p>
-
-<p><b><span style='font-size:10.0pt'>6. DISCLAIMER OF LIABILITY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
-THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>7. GENERAL</span></b> </p>
-
-<p><span style='font-size:10.0pt'>If any provision of this Agreement is invalid
-or unenforceable under applicable law, it shall not affect the validity or
-enforceability of the remainder of the terms of this Agreement, and without
-further action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.</span> </p>
-
-<p><span style='font-size:10.0pt'>If Recipient institutes patent litigation
-against any entity (including a cross-claim or counterclaim in a lawsuit)
-alleging that the Program itself (excluding combinations of the Program with
-other software or hardware) infringes such Recipient's patent(s), then such
-Recipient's rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed. </span></p>
-
-<p><span style='font-size:10.0pt'>All Recipient's rights under this Agreement
-shall terminate if it fails to comply with any of the material terms or
-conditions of this Agreement and does not cure such failure in a reasonable
-period of time after becoming aware of such noncompliance. If all Recipient's
-rights under this Agreement terminate, Recipient agrees to cease use and
-distribution of the Program as soon as reasonably practicable. However,
-Recipient's obligations under this Agreement and any licenses granted by
-Recipient relating to the Program shall continue and survive. </span></p>
-
-<p><span style='font-size:10.0pt'>Everyone is permitted to copy and distribute
-copies of this Agreement, but in order to avoid inconsistency the Agreement is
-copyrighted and may only be modified in the following manner. The Agreement
-Steward reserves the right to publish new versions (including revisions) of
-this Agreement from time to time. No one other than the Agreement Steward has
-the right to modify this Agreement. The Eclipse Foundation is the initial
-Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version
-of the Agreement will be given a distinguishing version number. The Program
-(including Contributions) may always be distributed subject to the version of
-the Agreement under which it was received. In addition, after a new version of
-the Agreement is published, Contributor may elect to distribute the Program
-(including its Contributions) under the new version. Except as expressly stated
-in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
-the intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.</span> </p>
-
-<p><span style='font-size:10.0pt'>This Agreement is governed by the laws of the
-State of New York and the intellectual property laws of the United States of
-America. No party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each party waives
-its rights to a jury trial in any resulting litigation.</span> </p>
-
-<p class=MsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>
-
-</div>
-
-</body>
-
-</html>
\ No newline at end of file
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.properties b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.properties
deleted file mode 100644
index 4ff28f9..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.properties
+++ /dev/null
@@ -1,157 +0,0 @@
-###############################################################################
-# Copyright (c) 2008 Dominik Schadow - http://www.xml-sicherheit.de
-# 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:
-#     Dominik Schadow - initial API and implementation
-###############################################################################
-featureName=XML Security Tools SDK Feature (Incubating)
-
-providerName=Eclipse Web Tools Platform
-
-description = XML Security Tools SDK Feature
-
-copyright =\
-Copyright (c) 2009 Dominik Schadow\n\
-All rights reserved. This program and the accompanying materials\n\
-are made available under the terms of the Eclipse Public License v1.0\n\
-which accompanies this distribution, and is available at\n\
-http://www.eclipse.org/legal/epl-v10.html\n\
-\n\
-Contributors:\n\
-    Dominik Schadow - initial API and implementation\n
-
-
-# "licenseURL" property - URL of the "Feature License"
-# do not translate value - just change to point to a locale-specific HTML page
-licenseURL=license.html
-
-# "license" property - text of the "Feature Update License"
-# should be plain text version of license agreement pointed to be "licenseURL"
-license=\
-Eclipse Foundation Software User Agreement\n\
-April 14, 2010\n\
-\n\
-Usage Of Content\n\
-\n\
-THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
-OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
-USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
-AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
-NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU\n\
-AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
-AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
-OR NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE\n\
-TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
-OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
-BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
-\n\
-Applicable Licenses\n\
-\n\
-Unless otherwise indicated, all Content made available by the\n\
-Eclipse Foundation is provided to you under the terms and conditions of\n\
-the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
-provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
-For purposes of the EPL, "Program" will mean the Content.\n\
-\n\
-Content includes, but is not limited to, source code, object code,\n\
-documentation and other files maintained in the Eclipse Foundation source code\n\
-repository ("Repository") in software modules ("Modules") and made available\n\
-as downloadable archives ("Downloads").\n\
-\n\
-       - Content may be structured and packaged into modules to facilitate delivering,\n\
-         extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
-         plug-in fragments ("Fragments"), and features ("Features").\n\
-       - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
-         in a directory named "plugins".\n\
-       - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
-         Each Feature may be packaged as a sub-directory in a directory named "features".\n\
-         Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
-         numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
-       - Features may also include other Features ("Included Features"). Within a Feature, files\n\
-         named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
-\n\
-The terms and conditions governing Plug-ins and Fragments should be\n\
-contained in files named "about.html" ("Abouts"). The terms and\n\
-conditions governing Features and Included Features should be contained\n\
-in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
-Licenses may be located in any directory of a Download or Module\n\
-including, but not limited to the following locations:\n\
-\n\
-       - The top-level (root) directory\n\
-       - Plug-in and Fragment directories\n\
-       - Inside Plug-ins and Fragments packaged as JARs\n\
-       - Sub-directories of the directory named "src" of certain Plug-ins\n\
-       - Feature directories\n\
-\n\
-Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
-Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
-Update License") during the installation process. If the Feature contains\n\
-Included Features, the Feature Update License should either provide you\n\
-with the terms and conditions governing the Included Features or inform\n\
-you where you can locate them. Feature Update Licenses may be found in\n\
-the "license" property of files named "feature.properties" found within a Feature.\n\
-Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
-terms and conditions (or references to such terms and conditions) that\n\
-govern your use of the associated Content in that directory.\n\
-\n\
-THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
-TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
-SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
-\n\
-       - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
-       - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
-       - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
-       - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
-       - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
-\n\
-IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
-TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
-is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
-govern that particular Content.\n\
-\n\
-\n\Use of Provisioning Technology\n\
-\n\
-The Eclipse Foundation makes available provisioning software, examples of which include,\n\
-but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
-the purpose of allowing users to install software, documentation, information and/or\n\
-other materials (collectively "Installable Software"). This capability is provided with\n\
-the intent of allowing such users to install, extend and update Eclipse-based products.\n\
-Information about packaging Installable Software is available at\n\
-http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
-\n\
-You may use Provisioning Technology to allow other parties to install Installable Software.\n\
-You shall be responsible for enabling the applicable license agreements relating to the\n\
-Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
-in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
-making it available in accordance with the Specification, you further acknowledge your\n\
-agreement to, and the acquisition of all necessary rights to permit the following:\n\
-\n\
-       1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
-          the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
-          extending or updating the functionality of an Eclipse-based product.\n\
-       2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
-          Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
-       3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
-          govern the use of the Installable Software ("Installable Software Agreement") and such\n\
-          Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
-          with the Specification. Such Installable Software Agreement must inform the user of the\n\
-          terms and conditions that govern the Installable Software and must solicit acceptance by\n\
-          the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
-          indication of agreement by the user, the provisioning Technology will complete installation\n\
-          of the Installable Software.\n\
-\n\
-Cryptography\n\
-\n\
-Content may contain encryption software. The country in which you are\n\
-currently may have restrictions on the import, possession, and use,\n\
-and/or re-export to another country, of encryption software. BEFORE\n\
-using any encryption software, please check the country's laws,\n\
-regulations and policies concerning the import, possession, or use, and\n\
-re-export of encryption software, to see if this is permitted.\n\
-\n\
-Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
-########### end of license property ##########################################
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.xml b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.xml
deleted file mode 100644
index 90870a2..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/feature.xml
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<feature
-      id="org.eclipse.wst.xml.security_sdk.feature"
-      label="%featureName"
-      version="0.5.0.qualifier"
-      provider-name="%providerName">
-
-   <description>
-      %description
-   </description>
-
-   <copyright>
-      %copyright
-   </copyright>
-
-   <license url="http://www.example.com/license">
-      [Enter License Description here.]
-   </license>
-
-
-   <includes
-         id="org.eclipse.wst.xml.security.feature"
-         version="0.0.0"/>
-            <includes
-         id="org.eclipse.wst.xml.security.feature.source"
-         version="0.0.0"/>
-
-</feature>
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/license.html b/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/license.html
deleted file mode 100644
index c184ca3..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_sdk.feature/license.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!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>Eclipse Foundation Software User Agreement</title>
-</head>
-
-<body lang="EN-US">
-<h2>Eclipse Foundation Software User Agreement</h2>
-<p>April 14, 2010</p>
-
-<h3>Usage Of Content</h3>
-
-<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
-   (COLLECTIVELY &quot;CONTENT&quot;).  USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
-   CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU AGREE THAT YOUR USE
-   OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
-   NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
-   CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
-
-<h3>Applicable Licenses</h3>
-
-<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation 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 provided with this Content and is also 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>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
-   repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
-
-<ul>
-       <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content.  Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
-       <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
-       <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.  Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;.  Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
-      and/or Fragments associated with that Feature.</li>
-       <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
-</ul>
-
-<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
-Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;).  Abouts and Feature Licenses may be located in any directory of a Download or Module
-including, but not limited to the following locations:</p>
-
-<ul>
-       <li>The top-level (root) directory</li>
-       <li>Plug-in and Fragment directories</li>
-       <li>Inside Plug-ins and Fragments packaged as JARs</li>
-       <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
-       <li>Feature directories</li>
-</ul>
-
-<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
-installation process.  If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
-inform you where you can locate them.  Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
-Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
-that directory.</p>
-
-<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.  SOME OF THESE
-OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
-
-<ul>
-       <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
-       <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
-       <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
-       <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
-       <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
-</ul>
-
-<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT.  If no About, Feature License, or Feature Update License is provided, please
-contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
-
-
-<h3>Use of Provisioning Technology</h3>
-
-<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
-   Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
-   other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
-   install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
-       href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
-   (&quot;Specification&quot;).</p>
-
-<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
-   applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
-   in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
-   Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
-
-<ol>
-       <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
-       on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
-       product.</li>
-       <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
-       accessed and copied to the Target Machine.</li>
-       <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
-       Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
-       Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
-       the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
-       indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
-</ol>
-
-<h3>Cryptography</h3>
-
-<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
-   another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
-   possession, or use, and re-export of encryption software, to see if this is permitted.</p>
-
-<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
-</body>
-</html>
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/.project b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/.project
deleted file mode 100644
index 5fd8c92..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/.project
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.wst.xml.security_tests.feature</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.FeatureBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.FeatureNature</nature>
-	</natures>
-</projectDescription>
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/build.properties b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/build.properties
deleted file mode 100644
index 6bcd28c..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/build.properties
+++ /dev/null
@@ -1,5 +0,0 @@
-bin.includes = feature.xml,\
-               feature.properties,\
-               license.html,\
-               epl-v10.html,\
-               eclipse_update_120.jpg
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/eclipse_update_120.jpg b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/eclipse_update_120.jpg
deleted file mode 100644
index bfdf708..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/eclipse_update_120.jpg
+++ /dev/null
Binary files differ
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/epl-v10.html b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/epl-v10.html
deleted file mode 100644
index ed4b196..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/epl-v10.html
+++ /dev/null
@@ -1,328 +0,0 @@
-<html xmlns:o="urn:schemas-microsoft-com:office:office"
-xmlns:w="urn:schemas-microsoft-com:office:word"
-xmlns="http://www.w3.org/TR/REC-html40">
-
-<head>
-<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
-<meta name=ProgId content=Word.Document>
-<meta name=Generator content="Microsoft Word 9">
-<meta name=Originator content="Microsoft Word 9">
-<link rel=File-List
-href="./Eclipse%20EPL%202003_11_10%20Final_files/filelist.xml">
-<title>Eclipse Public License - Version 1.0</title>
-<!--[if gte mso 9]><xml>
- <o:DocumentProperties>
-  <o:Revision>2</o:Revision>
-  <o:TotalTime>3</o:TotalTime>
-  <o:Created>2004-03-05T23:03:00Z</o:Created>
-  <o:LastSaved>2004-03-05T23:03:00Z</o:LastSaved>
-  <o:Pages>4</o:Pages>
-  <o:Words>1626</o:Words>
-  <o:Characters>9270</o:Characters>
-   <o:Lines>77</o:Lines>
-  <o:Paragraphs>18</o:Paragraphs>
-  <o:CharactersWithSpaces>11384</o:CharactersWithSpaces>
-  <o:Version>9.4402</o:Version>
- </o:DocumentProperties>
-</xml><![endif]--><!--[if gte mso 9]><xml>
- <w:WordDocument>
-  <w:TrackRevisions/>
- </w:WordDocument>
-</xml><![endif]-->
-<style>
-<!--
- /* Font Definitions */
-@font-face
-	{font-family:Tahoma;
-	panose-1:2 11 6 4 3 5 4 4 2 4;
-	mso-font-charset:0;
-	mso-generic-font-family:swiss;
-	mso-font-pitch:variable;
-	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
- /* Style Definitions */
-p.MsoNormal, li.MsoNormal, div.MsoNormal
-	{mso-style-parent:"";
-	margin:0in;
-	margin-bottom:.0001pt;
-	mso-pagination:widow-orphan;
-	font-size:12.0pt;
-	font-family:"Times New Roman";
-	mso-fareast-font-family:"Times New Roman";}
-p
-	{margin-right:0in;
-	mso-margin-top-alt:auto;
-	mso-margin-bottom-alt:auto;
-	margin-left:0in;
-	mso-pagination:widow-orphan;
-	font-size:12.0pt;
-	font-family:"Times New Roman";
-	mso-fareast-font-family:"Times New Roman";}
-p.BalloonText, li.BalloonText, div.BalloonText
-	{mso-style-name:"Balloon Text";
-	margin:0in;
-	margin-bottom:.0001pt;
-	mso-pagination:widow-orphan;
-	font-size:8.0pt;
-	font-family:Tahoma;
-	mso-fareast-font-family:"Times New Roman";}
-@page Section1
-	{size:8.5in 11.0in;
-	margin:1.0in 1.25in 1.0in 1.25in;
-	mso-header-margin:.5in;
-	mso-footer-margin:.5in;
-	mso-paper-source:0;}
-div.Section1
-	{page:Section1;}
--->
-</style>
-</head>
-
-<body lang=EN-US style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<p align=center style='text-align:center'><b>Eclipse Public License - v 1.0</b>
-</p>
-
-<p><span style='font-size:10.0pt'>THE ACCOMPANYING PROGRAM IS PROVIDED UNDER
-THE TERMS OF THIS ECLIPSE PUBLIC LICENSE (&quot;AGREEMENT&quot;). ANY USE,
-REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE
-OF THIS AGREEMENT.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>1. DEFINITIONS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Contribution&quot; means:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-in the case of the initial Contributor, the initial code and documentation
-distributed under this Agreement, and<br clear=left>
-b) in the case of each subsequent Contributor:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-changes to the Program, and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-additions to the Program;</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>where
-such changes and/or additions to the Program originate from and are distributed
-by that particular Contributor. A Contribution 'originates' from a Contributor
-if it was added to the Program by such Contributor itself or anyone acting on
-such Contributor's behalf. Contributions do not include additions to the
-Program which: (i) are separate modules of software distributed in conjunction
-with the Program under their own license agreement, and (ii) are not derivative
-works of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>&quot;Contributor&quot; means any person or
-entity that distributes the Program.</span> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Licensed Patents &quot; mean patent
-claims licensable by a Contributor which are necessarily infringed by the use
-or sale of its Contribution alone or when combined with the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>&quot;Program&quot; means the Contributions
-distributed in accordance with this Agreement.</span> </p>
-
-<p><span style='font-size:10.0pt'>&quot;Recipient&quot; means anyone who
-receives the Program under this Agreement, including all Contributors.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>2. GRANT OF RIGHTS</span></b> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-Subject to the terms of this Agreement, each Contributor hereby grants Recipient
-a non-exclusive, worldwide, royalty-free copyright license to<span
-style='color:red'> </span>reproduce, prepare derivative works of, publicly
-display, publicly perform, distribute and sublicense the Contribution of such
-Contributor, if any, and such derivative works, in source code and object code
-form.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-Subject to the terms of this Agreement, each Contributor hereby grants
-Recipient a non-exclusive, worldwide,<span style='color:green'> </span>royalty-free
-patent license under Licensed Patents to make, use, sell, offer to sell, import
-and otherwise transfer the Contribution of such Contributor, if any, in source
-code and object code form. This patent license shall apply to the combination
-of the Contribution and the Program if, at the time the Contribution is added
-by the Contributor, such addition of the Contribution causes such combination
-to be covered by the Licensed Patents. The patent license shall not apply to
-any other combinations which include the Contribution. No hardware per se is
-licensed hereunder. </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>c)
-Recipient understands that although each Contributor grants the licenses to its
-Contributions set forth herein, no assurances are provided by any Contributor
-that the Program does not infringe the patent or other intellectual property
-rights of any other entity. Each Contributor disclaims any liability to Recipient
-for claims brought by any other entity based on infringement of intellectual
-property rights or otherwise. As a condition to exercising the rights and
-licenses granted hereunder, each Recipient hereby assumes sole responsibility
-to secure any other intellectual property rights needed, if any. For example,
-if a third party patent license is required to allow Recipient to distribute
-the Program, it is Recipient's responsibility to acquire that license before
-distributing the Program.</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>d)
-Each Contributor represents that to its knowledge it has sufficient copyright
-rights in its Contribution, if any, to grant the copyright license set forth in
-this Agreement. </span></p>
-
-<p><b><span style='font-size:10.0pt'>3. REQUIREMENTS</span></b> </p>
-
-<p><span style='font-size:10.0pt'>A Contributor may choose to distribute the
-Program in object code form under its own license agreement, provided that:</span>
-</p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it complies with the terms and conditions of this Agreement; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b)
-its license agreement:</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>i)
-effectively disclaims on behalf of all Contributors all warranties and
-conditions, express and implied, including warranties or conditions of title
-and non-infringement, and implied warranties or conditions of merchantability
-and fitness for a particular purpose; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>ii)
-effectively excludes on behalf of all Contributors all liability for damages,
-including direct, indirect, special, incidental and consequential damages, such
-as lost profits; </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iii)
-states that any provisions which differ from this Agreement are offered by that
-Contributor alone and not by any other party; and</span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>iv)
-states that source code for the Program is available from such Contributor, and
-informs licensees how to obtain it in a reasonable manner on or through a
-medium customarily used for software exchange.<span style='color:blue'> </span></span></p>
-
-<p><span style='font-size:10.0pt'>When the Program is made available in source
-code form:</span> </p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>a)
-it must be made available under this Agreement; and </span></p>
-
-<p class=MsoNormal style='margin-left:.5in'><span style='font-size:10.0pt'>b) a
-copy of this Agreement must be included with each copy of the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Contributors may not remove or alter any
-copyright notices contained within the Program. </span></p>
-
-<p><span style='font-size:10.0pt'>Each Contributor must identify itself as the
-originator of its Contribution, if any, in a manner that reasonably allows
-subsequent Recipients to identify the originator of the Contribution. </span></p>
-
-<p><b><span style='font-size:10.0pt'>4. COMMERCIAL DISTRIBUTION</span></b> </p>
-
-<p><span style='font-size:10.0pt'>Commercial distributors of software may
-accept certain responsibilities with respect to end users, business partners
-and the like. While this license is intended to facilitate the commercial use
-of the Program, the Contributor who includes the Program in a commercial
-product offering should do so in a manner which does not create potential
-liability for other Contributors. Therefore, if a Contributor includes the
-Program in a commercial product offering, such Contributor (&quot;Commercial
-Contributor&quot;) hereby agrees to defend and indemnify every other
-Contributor (&quot;Indemnified Contributor&quot;) against any losses, damages and
-costs (collectively &quot;Losses&quot;) arising from claims, lawsuits and other
-legal actions brought by a third party against the Indemnified Contributor to
-the extent caused by the acts or omissions of such Commercial Contributor in
-connection with its distribution of the Program in a commercial product
-offering. The obligations in this section do not apply to any claims or Losses
-relating to any actual or alleged intellectual property infringement. In order
-to qualify, an Indemnified Contributor must: a) promptly notify the Commercial
-Contributor in writing of such claim, and b) allow the Commercial Contributor
-to control, and cooperate with the Commercial Contributor in, the defense and
-any related settlement negotiations. The Indemnified Contributor may participate
-in any such claim at its own expense.</span> </p>
-
-<p><span style='font-size:10.0pt'>For example, a Contributor might include the
-Program in a commercial product offering, Product X. That Contributor is then a
-Commercial Contributor. If that Commercial Contributor then makes performance
-claims, or offers warranties related to Product X, those performance claims and
-warranties are such Commercial Contributor's responsibility alone. Under this
-section, the Commercial Contributor would have to defend claims against the
-other Contributors related to those performance claims and warranties, and if a
-court requires any other Contributor to pay any damages as a result, the
-Commercial Contributor must pay those damages.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>5. NO WARRANTY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, THE PROGRAM IS PROVIDED ON AN &quot;AS IS&quot; BASIS, WITHOUT
-WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING,
-WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
-MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely
-responsible for determining the appropriateness of using and distributing the
-Program and assumes all risks associated with its exercise of rights under this
-Agreement , including but not limited to the risks and costs of program errors,
-compliance with applicable laws, damage to or loss of data, programs or
-equipment, and unavailability or interruption of operations. </span></p>
-
-<p><b><span style='font-size:10.0pt'>6. DISCLAIMER OF LIABILITY</span></b> </p>
-
-<p><span style='font-size:10.0pt'>EXCEPT AS EXPRESSLY SET FORTH IN THIS
-AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY
-OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF
-THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF
-THE POSSIBILITY OF SUCH DAMAGES.</span> </p>
-
-<p><b><span style='font-size:10.0pt'>7. GENERAL</span></b> </p>
-
-<p><span style='font-size:10.0pt'>If any provision of this Agreement is invalid
-or unenforceable under applicable law, it shall not affect the validity or
-enforceability of the remainder of the terms of this Agreement, and without
-further action by the parties hereto, such provision shall be reformed to the
-minimum extent necessary to make such provision valid and enforceable.</span> </p>
-
-<p><span style='font-size:10.0pt'>If Recipient institutes patent litigation
-against any entity (including a cross-claim or counterclaim in a lawsuit)
-alleging that the Program itself (excluding combinations of the Program with
-other software or hardware) infringes such Recipient's patent(s), then such
-Recipient's rights granted under Section 2(b) shall terminate as of the date
-such litigation is filed. </span></p>
-
-<p><span style='font-size:10.0pt'>All Recipient's rights under this Agreement
-shall terminate if it fails to comply with any of the material terms or
-conditions of this Agreement and does not cure such failure in a reasonable
-period of time after becoming aware of such noncompliance. If all Recipient's
-rights under this Agreement terminate, Recipient agrees to cease use and
-distribution of the Program as soon as reasonably practicable. However,
-Recipient's obligations under this Agreement and any licenses granted by
-Recipient relating to the Program shall continue and survive. </span></p>
-
-<p><span style='font-size:10.0pt'>Everyone is permitted to copy and distribute
-copies of this Agreement, but in order to avoid inconsistency the Agreement is
-copyrighted and may only be modified in the following manner. The Agreement
-Steward reserves the right to publish new versions (including revisions) of
-this Agreement from time to time. No one other than the Agreement Steward has
-the right to modify this Agreement. The Eclipse Foundation is the initial
-Agreement Steward. The Eclipse Foundation may assign the responsibility to
-serve as the Agreement Steward to a suitable separate entity. Each new version
-of the Agreement will be given a distinguishing version number. The Program
-(including Contributions) may always be distributed subject to the version of
-the Agreement under which it was received. In addition, after a new version of
-the Agreement is published, Contributor may elect to distribute the Program
-(including its Contributions) under the new version. Except as expressly stated
-in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
-the intellectual property of any Contributor under this Agreement, whether
-expressly, by implication, estoppel or otherwise. All rights in the Program not
-expressly granted under this Agreement are reserved.</span> </p>
-
-<p><span style='font-size:10.0pt'>This Agreement is governed by the laws of the
-State of New York and the intellectual property laws of the United States of
-America. No party to this Agreement will bring a legal action under this
-Agreement more than one year after the cause of action arose. Each party waives
-its rights to a jury trial in any resulting litigation.</span> </p>
-
-<p class=MsoNormal><![if !supportEmptyParas]>&nbsp;<![endif]><o:p></o:p></p>
-
-</div>
-
-</body>
-
-</html>
\ No newline at end of file
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.properties b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.properties
deleted file mode 100644
index 36612ce..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.properties
+++ /dev/null
@@ -1,157 +0,0 @@
-###############################################################################
-# Copyright (c) 2008 Dominik Schadow - http://www.xml-sicherheit.de
-# 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:
-#     Dominik Schadow - initial API and implementation
-###############################################################################
-featureName=XML Security Tools Tests Feature (Incubating)
-
-providerName=Eclipse Web Tools Platform
-
-description = XML Security Tools Tests Feature
-
-copyright =\
-Copyright (c) 2009 Dominik Schadow\n\
-All rights reserved. This program and the accompanying materials\n\
-are made available under the terms of the Eclipse Public License v1.0\n\
-which accompanies this distribution, and is available at\n\
-http://www.eclipse.org/legal/epl-v10.html\n\
-\n\
-Contributors:\n\
-    Dominik Schadow - initial API and implementation\n
-
-
-# "licenseURL" property - URL of the "Feature License"
-# do not translate value - just change to point to a locale-specific HTML page
-licenseURL=license.html
-
-# "license" property - text of the "Feature Update License"
-# should be plain text version of license agreement pointed to be "licenseURL"
-license=\
-Eclipse Foundation Software User Agreement\n\
-April 14, 2010\n\
-\n\
-Usage Of Content\n\
-\n\
-THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR\n\
-OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
-USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
-AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
-NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU\n\
-AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
-AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
-OR NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE\n\
-TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
-OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
-BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
-\n\
-Applicable Licenses\n\
-\n\
-Unless otherwise indicated, all Content made available by the\n\
-Eclipse Foundation is provided to you under the terms and conditions of\n\
-the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
-provided with this Content and is also available at http://www.eclipse.org/legal/epl-v10.html.\n\
-For purposes of the EPL, "Program" will mean the Content.\n\
-\n\
-Content includes, but is not limited to, source code, object code,\n\
-documentation and other files maintained in the Eclipse Foundation source code\n\
-repository ("Repository") in software modules ("Modules") and made available\n\
-as downloadable archives ("Downloads").\n\
-\n\
-       - Content may be structured and packaged into modules to facilitate delivering,\n\
-         extending, and upgrading the Content. Typical modules may include plug-ins ("Plug-ins"),\n\
-         plug-in fragments ("Fragments"), and features ("Features").\n\
-       - Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java(TM) ARchive)\n\
-         in a directory named "plugins".\n\
-       - A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.\n\
-         Each Feature may be packaged as a sub-directory in a directory named "features".\n\
-         Within a Feature, files named "feature.xml" may contain a list of the names and version\n\
-         numbers of the Plug-ins and/or Fragments associated with that Feature.\n\
-       - Features may also include other Features ("Included Features"). Within a Feature, files\n\
-         named "feature.xml" may contain a list of the names and version numbers of Included Features.\n\
-\n\
-The terms and conditions governing Plug-ins and Fragments should be\n\
-contained in files named "about.html" ("Abouts"). The terms and\n\
-conditions governing Features and Included Features should be contained\n\
-in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
-Licenses may be located in any directory of a Download or Module\n\
-including, but not limited to the following locations:\n\
-\n\
-       - The top-level (root) directory\n\
-       - Plug-in and Fragment directories\n\
-       - Inside Plug-ins and Fragments packaged as JARs\n\
-       - Sub-directories of the directory named "src" of certain Plug-ins\n\
-       - Feature directories\n\
-\n\
-Note: if a Feature made available by the Eclipse Foundation is installed using the\n\
-Provisioning Technology (as defined below), you must agree to a license ("Feature \n\
-Update License") during the installation process. If the Feature contains\n\
-Included Features, the Feature Update License should either provide you\n\
-with the terms and conditions governing the Included Features or inform\n\
-you where you can locate them. Feature Update Licenses may be found in\n\
-the "license" property of files named "feature.properties" found within a Feature.\n\
-Such Abouts, Feature Licenses, and Feature Update Licenses contain the\n\
-terms and conditions (or references to such terms and conditions) that\n\
-govern your use of the associated Content in that directory.\n\
-\n\
-THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER\n\
-TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.\n\
-SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):\n\
-\n\
-       - Common Public License Version 1.0 (available at http://www.eclipse.org/legal/cpl-v10.html)\n\
-       - Apache Software License 1.1 (available at http://www.apache.org/licenses/LICENSE)\n\
-       - Apache Software License 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)\n\
-       - Metro Link Public License 1.00 (available at http://www.opengroup.org/openmotif/supporters/metrolink/license.html)\n\
-       - Mozilla Public License Version 1.1 (available at http://www.mozilla.org/MPL/MPL-1.1.html)\n\
-\n\
-IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR\n\
-TO USE OF THE CONTENT. If no About, Feature License, or Feature Update License\n\
-is provided, please contact the Eclipse Foundation to determine what terms and conditions\n\
-govern that particular Content.\n\
-\n\
-\n\Use of Provisioning Technology\n\
-\n\
-The Eclipse Foundation makes available provisioning software, examples of which include,\n\
-but are not limited to, p2 and the Eclipse Update Manager ("Provisioning Technology") for\n\
-the purpose of allowing users to install software, documentation, information and/or\n\
-other materials (collectively "Installable Software"). This capability is provided with\n\
-the intent of allowing such users to install, extend and update Eclipse-based products.\n\
-Information about packaging Installable Software is available at\n\
-http://eclipse.org/equinox/p2/repository_packaging.html ("Specification").\n\
-\n\
-You may use Provisioning Technology to allow other parties to install Installable Software.\n\
-You shall be responsible for enabling the applicable license agreements relating to the\n\
-Installable Software to be presented to, and accepted by, the users of the Provisioning Technology\n\
-in accordance with the Specification. By using Provisioning Technology in such a manner and\n\
-making it available in accordance with the Specification, you further acknowledge your\n\
-agreement to, and the acquisition of all necessary rights to permit the following:\n\
-\n\
-       1. A series of actions may occur ("Provisioning Process") in which a user may execute\n\
-          the Provisioning Technology on a machine ("Target Machine") with the intent of installing,\n\
-          extending or updating the functionality of an Eclipse-based product.\n\
-       2. During the Provisioning Process, the Provisioning Technology may cause third party\n\
-          Installable Software or a portion thereof to be accessed and copied to the Target Machine.\n\
-       3. Pursuant to the Specification, you will provide to the user the terms and conditions that\n\
-          govern the use of the Installable Software ("Installable Software Agreement") and such\n\
-          Installable Software Agreement shall be accessed from the Target Machine in accordance\n\
-          with the Specification. Such Installable Software Agreement must inform the user of the\n\
-          terms and conditions that govern the Installable Software and must solicit acceptance by\n\
-          the end user in the manner prescribed in such Installable Software Agreement. Upon such\n\
-          indication of agreement by the user, the provisioning Technology will complete installation\n\
-          of the Installable Software.\n\
-\n\
-Cryptography\n\
-\n\
-Content may contain encryption software. The country in which you are\n\
-currently may have restrictions on the import, possession, and use,\n\
-and/or re-export to another country, of encryption software. BEFORE\n\
-using any encryption software, please check the country's laws,\n\
-regulations and policies concerning the import, possession, or use, and\n\
-re-export of encryption software, to see if this is permitted.\n\
-\n\
-Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.\n
-########### end of license property ##########################################
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.xml b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.xml
deleted file mode 100644
index 1128dee..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/feature.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<feature
-      id="org.eclipse.wst.xml.security_tests.feature"
-      label="%featureName"
-      version="0.5.0.qualifier"
-      provider-name="%providerName">
-
-   <description>
-      %description
-   </description>
-
-   <copyright>
-      %copyright
-   </copyright>
-
-   <license url="%licenseURL">
-      %license
-   </license>
-
-
-   <plugin
-         id="org.eclipse.wst.xml.security.core.tests"
-         download-size="0"
-         install-size="0"
-         version="0.0.0"
-         />
-
-   <plugin
-         id="org.eclipse.wst.xml.security.ui.tests"
-         download-size="0"
-         install-size="0"
-         version="0.0.0"
-         />
-
-</feature>
diff --git a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/license.html b/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/license.html
deleted file mode 100644
index c184ca3..0000000
--- a/sourceediting/features/org.eclipse.wst.xml.security_tests.feature/license.html
+++ /dev/null
@@ -1,107 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1" ?>
-<!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>Eclipse Foundation Software User Agreement</title>
-</head>
-
-<body lang="EN-US">
-<h2>Eclipse Foundation Software User Agreement</h2>
-<p>April 14, 2010</p>
-
-<h3>Usage Of Content</h3>
-
-<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
-   (COLLECTIVELY &quot;CONTENT&quot;).  USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
-   CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU AGREE THAT YOUR USE
-   OF THE CONTENT IS GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR
-   NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
-   CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT USE THE CONTENT.</p>
-
-<h3>Applicable Licenses</h3>
-
-<p>Unless otherwise indicated, all Content made available by the Eclipse Foundation 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 provided with this Content and is also 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>Content includes, but is not limited to, source code, object code, documentation and other files maintained in the Eclipse Foundation source code
-   repository (&quot;Repository&quot;) in software modules (&quot;Modules&quot;) and made available as downloadable archives (&quot;Downloads&quot;).</p>
-
-<ul>
-       <li>Content may be structured and packaged into modules to facilitate delivering, extending, and upgrading the Content.  Typical modules may include plug-ins (&quot;Plug-ins&quot;), plug-in fragments (&quot;Fragments&quot;), and features (&quot;Features&quot;).</li>
-       <li>Each Plug-in or Fragment may be packaged as a sub-directory or JAR (Java&trade; ARchive) in a directory named &quot;plugins&quot;.</li>
-       <li>A Feature is a bundle of one or more Plug-ins and/or Fragments and associated material.  Each Feature may be packaged as a sub-directory in a directory named &quot;features&quot;.  Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of the Plug-ins
-      and/or Fragments associated with that Feature.</li>
-       <li>Features may also include other Features (&quot;Included Features&quot;). Within a Feature, files named &quot;feature.xml&quot; may contain a list of the names and version numbers of Included Features.</li>
-</ul>
-
-<p>The terms and conditions governing Plug-ins and Fragments should be contained in files named &quot;about.html&quot; (&quot;Abouts&quot;). The terms and conditions governing Features and
-Included Features should be contained in files named &quot;license.html&quot; (&quot;Feature Licenses&quot;).  Abouts and Feature Licenses may be located in any directory of a Download or Module
-including, but not limited to the following locations:</p>
-
-<ul>
-       <li>The top-level (root) directory</li>
-       <li>Plug-in and Fragment directories</li>
-       <li>Inside Plug-ins and Fragments packaged as JARs</li>
-       <li>Sub-directories of the directory named &quot;src&quot; of certain Plug-ins</li>
-       <li>Feature directories</li>
-</ul>
-
-<p>Note: if a Feature made available by the Eclipse Foundation is installed using the Provisioning Technology (as defined below), you must agree to a license (&quot;Feature Update License&quot;) during the
-installation process.  If the Feature contains Included Features, the Feature Update License should either provide you with the terms and conditions governing the Included Features or
-inform you where you can locate them.  Feature Update Licenses may be found in the &quot;license&quot; property of files named &quot;feature.properties&quot; found within a Feature.
-Such Abouts, Feature Licenses, and Feature Update Licenses contain the terms and conditions (or references to such terms and conditions) that govern your use of the associated Content in
-that directory.</p>
-
-<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND CONDITIONS.  SOME OF THESE
-OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT ARE NOT LIMITED TO):</p>
-
-<ul>
-       <li>Common Public License Version 1.0 (available at <a href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)</li>
-       <li>Apache Software License 1.1 (available at <a href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)</li>
-       <li>Apache Software License 2.0 (available at <a href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)</li>
-       <li>Metro Link Public License 1.00 (available at <a href="http://www.opengroup.org/openmotif/supporters/metrolink/license.html">http://www.opengroup.org/openmotif/supporters/metrolink/license.html</a>)</li>
-       <li>Mozilla Public License Version 1.1 (available at <a href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)</li>
-</ul>
-
-<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS PRIOR TO USE OF THE CONTENT.  If no About, Feature License, or Feature Update License is provided, please
-contact the Eclipse Foundation to determine what terms and conditions govern that particular Content.</p>
-
-
-<h3>Use of Provisioning Technology</h3>
-
-<p>The Eclipse Foundation makes available provisioning software, examples of which include, but are not limited to, p2 and the Eclipse
-   Update Manager (&quot;Provisioning Technology&quot;) for the purpose of allowing users to install software, documentation, information and/or
-   other materials (collectively &quot;Installable Software&quot;). This capability is provided with the intent of allowing such users to
-   install, extend and update Eclipse-based products. Information about packaging Installable Software is available at <a
-       href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
-   (&quot;Specification&quot;).</p>
-
-<p>You may use Provisioning Technology to allow other parties to install Installable Software. You shall be responsible for enabling the
-   applicable license agreements relating to the Installable Software to be presented to, and accepted by, the users of the Provisioning Technology
-   in accordance with the Specification. By using Provisioning Technology in such a manner and making it available in accordance with the
-   Specification, you further acknowledge your agreement to, and the acquisition of all necessary rights to permit the following:</p>
-
-<ol>
-       <li>A series of actions may occur (&quot;Provisioning Process&quot;) in which a user may execute the Provisioning Technology
-       on a machine (&quot;Target Machine&quot;) with the intent of installing, extending or updating the functionality of an Eclipse-based
-       product.</li>
-       <li>During the Provisioning Process, the Provisioning Technology may cause third party Installable Software or a portion thereof to be
-       accessed and copied to the Target Machine.</li>
-       <li>Pursuant to the Specification, you will provide to the user the terms and conditions that govern the use of the Installable
-       Software (&quot;Installable Software Agreement&quot;) and such Installable Software Agreement shall be accessed from the Target
-       Machine in accordance with the Specification. Such Installable Software Agreement must inform the user of the terms and conditions that govern
-       the Installable Software and must solicit acceptance by the end user in the manner prescribed in such Installable Software Agreement. Upon such
-       indication of agreement by the user, the provisioning Technology will complete installation of the Installable Software.</li>
-</ol>
-
-<h3>Cryptography</h3>
-
-<p>Content may contain encryption software. The country in which you are currently may have restrictions on the import, possession, and use, and/or re-export to
-   another country, of encryption software. BEFORE using any encryption software, please check the country's laws, regulations and policies concerning the import,
-   possession, or use, and re-export of encryption software, to see if this is permitted.</p>
-
-<p><small>Java and all Java-based trademarks are trademarks of Oracle Corporation in the United States, other countries, or both.</small></p>
-</body>
-</html>