Update documentation for 1.5.0 release.
diff --git a/tooling-guide/images/editor-overview-page.png b/tooling-guide/images/editor-overview-page.png
index 7343c72..af1bfdf 100644
--- a/tooling-guide/images/editor-overview-page.png
+++ b/tooling-guide/images/editor-overview-page.png
Binary files differ
diff --git a/tooling-guide/images/migrate_plugin.png b/tooling-guide/images/migrate_plugin.png
new file mode 100644
index 0000000..52e72b6
--- /dev/null
+++ b/tooling-guide/images/migrate_plugin.png
Binary files differ
diff --git a/tooling-guide/images/new_pde_bundle.png b/tooling-guide/images/new_pde_bundle.png
new file mode 100644
index 0000000..4de6ed9
--- /dev/null
+++ b/tooling-guide/images/new_pde_bundle.png
Binary files differ
diff --git a/tooling-guide/images/new_server_wiz_1.png b/tooling-guide/images/new_server_wiz_1.png
new file mode 100644
index 0000000..a3f730f
--- /dev/null
+++ b/tooling-guide/images/new_server_wiz_1.png
Binary files differ
diff --git a/tooling-guide/images/new_server_wiz_2.png b/tooling-guide/images/new_server_wiz_2.png
new file mode 100644
index 0000000..b49fccc
--- /dev/null
+++ b/tooling-guide/images/new_server_wiz_2.png
Binary files differ
diff --git a/tooling-guide/images/new_server_wiz_3.png b/tooling-guide/images/new_server_wiz_3.png
new file mode 100644
index 0000000..18211fd
--- /dev/null
+++ b/tooling-guide/images/new_server_wiz_3.png
Binary files differ
diff --git a/tooling-guide/images/pde_bundle_wiz.png b/tooling-guide/images/pde_bundle_wiz.png
new file mode 100644
index 0000000..dca7cda
--- /dev/null
+++ b/tooling-guide/images/pde_bundle_wiz.png
Binary files differ
diff --git a/tooling-guide/images/pde_bundle_wiz_2.png b/tooling-guide/images/pde_bundle_wiz_2.png
new file mode 100644
index 0000000..173f51a
--- /dev/null
+++ b/tooling-guide/images/pde_bundle_wiz_2.png
Binary files differ
diff --git a/tooling-guide/images/servers_and_editor.png b/tooling-guide/images/servers_and_editor.png
new file mode 100644
index 0000000..c9550c2
--- /dev/null
+++ b/tooling-guide/images/servers_and_editor.png
Binary files differ
diff --git a/tooling-guide/images/virgo_target_platform.png b/tooling-guide/images/virgo_target_platform.png
new file mode 100644
index 0000000..ee6c026
--- /dev/null
+++ b/tooling-guide/images/virgo_target_platform.png
Binary files differ
diff --git a/tooling-guide/src/developing_with_PDE.xml b/tooling-guide/src/developing_with_PDE.xml
new file mode 100644
index 0000000..469c635
--- /dev/null
+++ b/tooling-guide/src/developing_with_PDE.xml
@@ -0,0 +1,182 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
+<chapter id="developing_with_PDE">
+	<title>Developing OSGi Bundles using Plug-in Development Environment
+		(PDE)
+	</title>
+	This chapter assumes that the user is already familiar with the Plug-in Development Environment (PDE). Should this not be the case
+	it is recommended to read first the PDE documentation or one of the many tutorials available online.
+	<section id="pde_dependencies">
+		<title>Resolving Bundle Dependencies</title>
+		<para>
+			Starting from release 1.5.0 the Tools support developing OSGi
+			Bundles using the widely popular Eclipse Plug-in Development
+			Environment (PDE).
+		</para>
+		<para>
+			While working with OSGi bundles, one of the most important
+			aspects is defining the required dependencies in the MANIFEST.MF file. 
+			When used in conjunction with the PDE, the Virgo Tools address this problem
+			by leveraging on the PDE tooling and in particular on the PDE Target Platform Definition.
+			A Target Platform Definition defines the bundles which your workspace will be built against.
+		</para>
+		<para>
+			At runtime however, a PDE Target Platform won't be available and
+			dependency resolution will always occur against the bundle
+			repositories configured for the @umbrella.product.name@. The Tools
+			try to bridge runtime and development by providing a Server
+			wizard that creates a new PDE Target Platform Definition that
+			matches the Server repository configuration,
+			as defined in
+			<code>org.eclipse.virgo.repository.properties</code>
+			.
+		</para>
+		<para>
+			The @umbrella.product.name@ supports watched, external and remote
+			repositories. Watched and external repositories correspond to
+			file system folders, while a remote repository is a remote Virgo
+			instance that can serve its repository content to other Virgo instances 
+			for the purpose of dependency resolution. The PDE Target Platform allows its content
+			to be specified only as file system folders or P2 Update sites. As such, when the Tools create a
+			PDE Target Platform Definition from the runtime repository configuration only watched and 
+			external repositories are considered.
+		<para>
+			Developers should properly setup a local @umbrella.product.name@ so that its bundle repositories
+			contain their application dependencies. Then they should use the Tools to setup a PDE Target Platform
+			so that their workspace projects are build and resolved against the same bundles that will be available
+			at runtime.			 
+		</para>
+		<note>
+			Note that when using the Tools together with PDE to develop for
+			Virgo it's not possible to use the MANIFEST.MF headers
+			<code>Import-Bundle</code>
+			(not part of the standard OSGi specification but supported by
+			Virgo)
+			and <code>Require-Bundle</code>
+			(part of the standard OSGi specification but not supported by Virgo).
+			Developers will have to declare all of their external dependencies
+			using the
+			<code>Import-Package</code>
+			header only.
+		</note>			
+		</para>
+	</section>
+	<section id="runtime-wizard">
+		<title>Server Runtime Wizard</title>
+		<para>
+			After installing the Virgo Tools in Eclipse it is possible
+			to create a new Server.
+			A Server can be created from the global <emphasis>New</emphasis> dialog, by selecting the
+			<emphasis>Virgo Runtime</emphasis> item within the <emphasis>EclipseRT</emphasis> category.
+			Alternatively, users can right click over the <emphasis>Servers</emphasis> view (easily accessible from
+			the <emphasis>Virgo</emphasis> perspective or via <emphasis>New -> Show View -> Other</emphasis>) and select <emphasis>New</emphasis> to
+			open the same wizard.
+		</para>
+		<para>
+			<imagedata fileref="images/new_server_wiz_1.png" format="PNG" />			
+		</para>
+		<para>
+			In both cases the Server wizard will appear and will ask the user
+			to select a valid Virgo installation from the local file system.
+			<note>
+			The first time a Server is created in a new workspace the wizard
+			will create both a Server instance and a Server Runtime. 
+			The former corresponds to the Server where the bundles in the workspace will be deployed,
+			the latter corresponds to the runtime definition of which the former will be an instance.
+			</note>
+			<note>
+			While it's in theory possible to create multiple runtimes and different Server instances
+			associated to them within a single workspace, only one PDE target platform can be active in a workspace at a time.			
+			As such when working with the Virgo Tools and PDE it is recommended to use one dedicated Eclipse workspace
+			for one Server runtime and one PDE Target Platform.</note>			
+		</para>		
+		<para>
+			<imagedata fileref="images/new_server_wiz_2.png" format="PNG" />
+		</para>		
+		<para>
+			To manage bundle dependencies with PDE make sure to select the check-box in the next page of the wizard:
+		</para>
+		<para>
+			<imagedata fileref="images/new_server_wiz_3.png" format="PNG" />
+		</para>
+		<para>
+			The wizard will then parse the <code>org.eclipse.virgo.repository.properties</code> file and show to the
+			user the folders that will be used for setting up the PDE Target Platform definition.
+		    In this page it's possible to include additional folders before pressing <emphasis>Finish</emphasis>.
+			The folders visible in the picture above are the default content of an unchanged <code>org.eclipse.virgo.repository.properties</code> file plus the server <emphasis>plugins</emphasis> folder
+			contained in the server home directory. In reality the <emphasis>plugins</emphasis> folder is not a bundle repository and is not listed in the <code>org.eclipse.virgo.repository.properties</code> file.
+			It contains some core components of the @umbrella.product.name@ and gets included in the Target Platform definition
+			because at runtime the contained bundles are made available to the deployed applications for dependencies resolution.  
+		</para><para>			
+			Additional folders can be added (or removed if already present in the <code>org.eclipse.virgo.repository.properties</code> file). When the <emphasis>Finish</emphasis> button
+			is pressed the wizard will create a PDE Target Platform definition and will offer to modify <code>org.eclipse.virgo.repository.properties</code> to reflect any change applied by the user.
+			The newly created Target Platform will be named after the Server runtime (usually "Virgo Runtime" if not changed by the user in the previous wizard page).		
+		<note>		
+			Note that while it's safe to include additional folders, users should not remove the default folders unless they really know what they are doing.
+			</note>
+		</para>
+		<para>
+			It is possible to double check the content of the newly created PDE Target Platform via the Target Platform preferences page in the
+			Preferences dialog (<emphasis>Window -> Preferences</emphasis>):
+		</para>
+		<para><imagedata fileref="images/virgo_target_platform.png" format="PNG" /></para>
+		<para>
+			The target platform name must match the Server runtime name ("Virgo Runtime" in this example) for the Virgo Tools to be able to correlate
+			the two. 
+			<note>When a PDE Target platform exists for a Virgo Server instance and is named like the corresponding Virgo Runtime, the Server icon
+			is decorated in the <emphasis>Servers</emphasis> view with a tiny plug-in icon in the top-left, as depicted below.</note> 		
+		</para>
+		<para><imagedata fileref="images/servers_and_editor.png" format="PNG" /></para>
+		<para>
+		As visible in the above picture, the <emphasis>Server editor</emphasis>, which is easily accessible by double-clicking over the @umbrella.product.name@
+		in the <emphasis>Server</emphasis> view, provides an new section titled <emphasis>Target Platform</emphasis> which allows reloading the
+		content of the Target Platform definition associated to the current server (useful for example when new bundles are added to the repository)
+		and allows editing the content of the current Target Platform definition by recalling the same UI of the last page of the server creation wizard.
+		</para>
+	</section>
+	<section id="pde-projects">
+	<title>PDE Bundle projects</title>
+	<para>
+		Now that the @umbrella.product.name@ has been properly setup in the Eclipse workspace, including the corresponding PDE Target Platform definition,
+		it's finally possible to create new projects.
+	</para>
+	<para>The Virgo Tools require PDE Plug-in projects to be augmented with some additional features to be usable. As such, in order to create
+	a new project it is necessary to use the dedicated wizard named <emphasis>PDE Bundle project</emphasis> located within the <emphasis>Virgo</emphasis>
+	category:
+	</para>
+	<para><imagedata fileref="images/pde_bundle_wiz.png" format="PNG" /></para>		
+	<para>
+		The above wizard is the standard PDE <emphasis>Plug-in project</emphasis> wizard with some choices disabled or defaulted.
+		In addition to the usual pages it includes an extra page where the user can optionally specify a Web context root.
+		If a context root is specified the new project will be a Web Application bundle (WAB). If the context root is not specified
+		the new project will be a regular OSGi bundle. 
+		<note>
+			The icon of Plug-in projects created for Virgo using the above wizard will be decorated with a tiny <emphasis>EclipseRT globe</emphasis> in the top left.
+		</note>
+		<para><imagedata fileref="images/new_pde_bundle.png" format="PNG" /></para>			
+	</para>
+	<para><note>
+		Once a <emphasis>PDE Bundle project</emphasis> has been created as explained above, the developer can use the standard <emphasis>PDE Plug-in Editor</emphasis>
+		and related tooling to work with the newly created project. Please refer to the official PDE documentation for further details.</note> 
+	</para>
+	</section>
+	<section id="pde-migration-actions">
+		<title>Migration actions</title>
+		<para>
+		Before the Virgo Tools provided support for PDE, some developers where using an unofficial Eclipse plug-in called  
+		<ulink url="http://github.com/giamma/PDE2Virgo">PDE2Virgo</ulink>.
+		The Virgo Tools provide a migration action for migrating PDE2Virgo projects into <emphasis>PDE bundle projects</emphasis>.
+		The migration action is accessible via <emphasis>Virgo</emphasis> context menu and is labeled <emphasis>Migrate PDE2Virgo project</emphasis>.
+		The action is visible when the selection contains only <emphasis>PDE2Virgo</emphasis> projects and supports multiple selection.
+		</para>
+		<para>
+		A migration action is also provided for PDE users who want to migrate PDE <emphasis>Plug-in</emphasis> projects to <emphasis>PDE bundle projects</emphasis> to be
+		able to run their projects on a Virgo test environment integrated in Eclipse.  
+		The migration action is accessible via <emphasis>Virgo</emphasis> context menu and is labeled <emphasis>Migrate Plug-in project</emphasis>.
+		The action is visible when the selection contains only <emphasis>Plug-in</emphasis> projects and supports multiple selection.
+		</para>		
+		<para><imagedata fileref="images/migrate_plugin.png" format="PNG" /></para>	
+	</section>
+</chapter>
+
+
diff --git a/tooling-guide/src/introduction.xml b/tooling-guide/src/introduction.xml
index 00d3e09..67d3176 100644
--- a/tooling-guide/src/introduction.xml
+++ b/tooling-guide/src/introduction.xml
@@ -10,4 +10,7 @@
 		the conversion of existing projects into OSGi bundle projects. Projects can then be deployed and debugged on a running
 		@umbrella.product.name.short@ from within Eclipse.
 	</para>
+	<para>Besides its OSGi bundle projects, starting from version 1.5 Virgo Tools support usage of Plug-in Development
+		Environment (Eclipse PDE) for developing projects that can be deployed and debugged on a running @umbrella.product.name.short@ from within Eclipse.
+	</para>	
 </chapter>
diff --git a/tooling-guide/src/server-editor.xml b/tooling-guide/src/server-editor.xml
index 30efe5d..0a57f25 100644
--- a/tooling-guide/src/server-editor.xml
+++ b/tooling-guide/src/server-editor.xml
@@ -15,9 +15,36 @@
 			<imagedata fileref="images/editor-overview-page.png" format="PNG" />
 		</para>
 		<para>
-			See the
+		     The overview page contains several sections. Some of them are inherited by the Web Tools Platform while other
+		     are contributed specifically by the Virgo Tools.
+		    <itemizedlist>
+			 	<listitem>The <emphasis>Target Platform</emphasis> section has been introduced in release 1.5 and provides shortcuts
+			 	for editing or reloading the PDE Target Platform associated to the current @umbrella.product.name@. 
+			 	</listitem>		    
+			 	<listitem>The <emphasis>Redeploy Behavior</emphasis> section allows the user to specify files that should be copied
+			 	into the server without redeploying the bundle. This is typically used to speed up publishing operations for static files. 
+			 	</listitem>
+			 	<listitem>The <emphasis>Publishing</emphasis> section allows the user to select when changed resources should be published
+			 	to the running server. 
+			 	</listitem>
+				<listitem>The <emphasis>Timeouts</emphasis> section allows the user to configure the server startup and shutdown timeout.
+			 	</listitem>
+				<listitem>The <emphasis>Deployer Control</emphasis> section allows the user to configure the parameters of the JMX communication
+				between the Virgo Tools and the @umbrella.product.name@.
+			 	</listitem>
+			 	<listitem>The <emphasis>Artefact Deployment Order</emphasis> section allows the user to configure the activation order of the artefacts
+			 	deployed into the @umbrella.product.name@. Multi-selection is supported.
+			 	</listitem>
+			 	<listitem>The <emphasis>Server Startup Configuration</emphasis> section allows the user to configure statup parameters of 
+			 	the @umbrella.product.name@. The <emphasis>-clean</emphasis> options if checked forces the cleaning of the @umbrella.product.name@
+			 	temporary folders at every startup. 
+			 	</listitem>			 	
+			</itemizedlist>
+		</para>
+		<para>
+			See the 
 			<emphasis>Web Tools Platform Guide</emphasis>
-			for more information on what the various configuration options do.
+			for more information on the other configuration sections.
 		</para>
 	</section>
 	<section>
diff --git a/tooling-guide/src/virgo-tooling-guide.xml b/tooling-guide/src/virgo-tooling-guide.xml
index 8c1e226..9244395 100644
--- a/tooling-guide/src/virgo-tooling-guide.xml
+++ b/tooling-guide/src/virgo-tooling-guide.xml
@@ -59,9 +59,14 @@
 				<firstname>Leo</firstname>
 				<surname>Dos Santos</surname>
 			</author>
+			<author>
+				<firstname>GianMaria</firstname>
+				<surname>Romanato</surname>
+			</author>			
 		</authorgroup>
 		<legalnotice>
 			<para>Copyright &copy; 2012 VMware Inc.</para>
+			<para>Copyright &copy; 2016 GianMaria Romanato</para>
 		</legalnotice>
 	</bookinfo>
 
@@ -72,6 +77,7 @@
 	<xi:include href="perspective-views.xml" />
 	<xi:include href="server-editor.xml" />
 	<xi:include href="developing.xml" />
+	<xi:include href="developing_with_PDE.xml" />
 	<xi:include href="pars.xml" />
 	<xi:include href="deploying.xml" />
 	<xi:include href="wiki.xml" />
diff --git a/tooling-guide/src/whatsnew.xml b/tooling-guide/src/whatsnew.xml
index dfa82ab..aae8627 100644
--- a/tooling-guide/src/whatsnew.xml
+++ b/tooling-guide/src/whatsnew.xml
@@ -1,6 +1,41 @@
 <?xml version='1.0' ?><!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <chapter id="What.27s_New">
 	<title>What's New</title>
+	<section id="1.5.0_Release">
+		<title>1.5.0 Release</title>
+		<section id="UI_15">
+			<title>UI</title>
+			<para>Starting from version 1.5 it is possible to develop for the Virgo Runtime
+			using the Eclipse Plug-in Development Environment (PDE). See the Tooling Guide for more information on this new feature.
+			</para>
+			<section id="Wizards">
+				<title>Wizards</title>
+				<section id="Server_Runtime_Wizard">
+					<title>Server Runtime Wizard</title>
+					<para>The Server Runtime Wizard can now optionally assist the user in setting up a PDE Target Platform definition whose content reflects the
+						Virgo Runtime repository configuration.
+					</para>
+				</section>
+				<section id="PDE_Project_Wizard">
+					<title>PDE Project Wizard</title>
+					<para>A new project wizard allows creating PDE Plug-in projects that are also Virgo Runtime projects and can be deployed on a Virgo Server
+					</para>
+				</section>
+			</section>
+			<section id="Server_Editor">
+				<title>Server Editor</title>
+				<para>The Server Editor has been improved to:</para>
+				<itemizedlist>
+				<listitem>
+					<para>provide proper support for PDE Target Platform definitions</para>
+				</listitem>
+				<listitem>
+					<para>allow multi-selection in the 'Artefact Deployment Order' section.</para>
+				</listitem>
+			</itemizedlist>
+			</section>
+		</section>
+	</section>	
 	<section id="1.0.0_Release">
 		<title>1.0.0 Release</title>
 		<section id="UI">
diff --git a/tooling-guide/src/wiki.xml b/tooling-guide/src/wiki.xml
index ee288ac..b5b8bf1 100644
--- a/tooling-guide/src/wiki.xml
+++ b/tooling-guide/src/wiki.xml
@@ -18,6 +18,9 @@
 				<para>Web Bundles </para>
 			</listitem>
 			<listitem>
+				<para>New from release 1.5.0: PDE Plug-in projects (created via a dedicated Wizard)</para>
+			</listitem>						
+			<listitem>
 				<para>Deployment to a Virgo Server in the server view.</para>
 			</listitem>
 		</itemizedlist>
@@ -77,32 +80,11 @@
 		<title>Known Issues</title>
 		<itemizedlist>
 			<listitem>
-				<para>The Virgo tools currently do not support Eclipse 3.6 (Helios) and derived Spring Source products. 
-					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=377236">https://bugs.eclipse.org/bugs/show_bug.cgi?id=377236</ulink>.
-				</para>
-			</listitem>
-			<listitem>
-				<para>An exception occurs when you click on an item in the Bundle Overview. This is a Libra issue that will be fixed when the next Libra build occurs. 
-					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=377582">https://bugs.eclipse.org/bugs/show_bug.cgi?id=377582</ulink>.
-				</para>
-			</listitem>
-			<listitem>
 				<para>Manifest generation does not seem to be working properly. 
 					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379233">https://bugs.eclipse.org/bugs/show_bug.cgi?id=379233</ulink>
 				</para>
 			</listitem>
 			<listitem>
-				<para>The greenpages sample does not work. We're not yet sure if this is a tooling or runtime issue. 
-					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=368781">https://bugs.eclipse.org/bugs/show_bug.cgi?id=368781</ulink> 
-				</para>
-			</listitem>
-			<listitem>
-				<para>If you have existing Virgo server defined you will see nasty exceptions. Just follow the instructions 
-					<link linkend="Server_Versions">below</link> 
-					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=379282">https://bugs.eclipse.org/bugs/show_bug.cgi?id=379282</ulink>
-				</para>
-			</listitem>
-			<listitem>
 				<para>Other significant bugs still exist. Please see these release train bugs for a current list, and please report any other issues you discover:</para>
 				<itemizedlist>
 					<listitem>
@@ -129,156 +111,6 @@
 			</listitem>
 		</itemizedlist>
 	</section>
-	<section id="Migration">
-		<title>Migration</title>
-		<section id="From_Pre_M2_to_M4">
-			<title>From Pre M2 to M4</title>
-			<section id="Server_Versions">
-				<title>Server Versions</title>
-				<para>The good news: We have done away with the need for managing multiple server versions. This also means that we won't have to support multiple WebTools Server Runtimes and Servers which will make adding new servers and variants much easier. See 
-					<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=373453">https://bugs.eclipse.org/bugs/show_bug.cgi?id=373453</ulink> for more details.
-				</para>
-				<para>The bad news: Any Server Runtimes that you already created for Virgo Server 3.5 will not work -- and you will see nasty exceptions if you try to use them. But since pre-M4 Virgo Tooling didn't work with Virgo Server 3.5 
-					<emphasis role="italic">anyway</emphasis>, this should be a moot issue for most people.
-				</para>
-				<para>What to do: If you have an existing (i.e., created using Virgo IDE installed before 10 March 2012) Virgo Server 3.5 Runtime defined, just delete it and replace it with a new Virgo Runtime in 
-					<emphasis role="italic">Preferences:Server:Runtime Environments</emphasis>. You'll see that the correct version is discovered automatically. Then, open any Servers that uses the old runtime and select the new one from the Runtime Environment popup menu.
-				</para>
-			</section>
-		</section>
-		<section id="From_Spring_Source_and_Virgo_2.x_Tooling">
-			<title>From Spring Source and Virgo 2.x Tooling</title>
-			<para>Moving from the old tooling to the new requires some changes to your existing projects, these are documented here. </para>
-			<para>The Bundlor .settings file has a new name (
-				<emphasis role="italic">com.springsource.server.ide.bundlor.core.prefs</emphasis> -&amp;gt; 
-				<emphasis role="italic">org.eclipse.virgo.ide.bundlor.core.prefs</emphasis>) and the property keys in it have new names as well. Currently these just need to be changed manually (replace 
-				<emphasis role="italic">com.springsource.server</emphasis> by 
-				<emphasis role="italic">org.eclipse.virgo</emphasis>) 
-				<emphasis role="bold">or use the project properties pane to create new settings and delete the old one.</emphasis> (recommended)
-			</para>
-			<para>The Bundle Dependencies classpath entry has a new name (
-				<emphasis role="italic">com.springsource.server.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER</emphasis> -&amp;gt; 
-				<emphasis role="italic">org.eclipse.virgo.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER</emphasis>). This can be changed manually (in the .classpath file) or in the Java Build Path section of the project properties. 
-			</para>
-			<para>The attributes used to mark folders as test folders have been renamed (
-				<emphasis role="italic">com.springsource.server.ide.jdt.core.test.classpathentry</emphasis> -&amp;gt; 
-				<emphasis role="italic">org.eclipse.virgo.ide.jdt.core.test.classpathentry</emphasis>). This can be changed manually (in the .classpath file). 
-			</para>
-			<para>The PAR and Bundle nature have been renamed (
-				<emphasis role="italic">com.springsource.server.ide.facet.core.bundlenature</emphasis> -&amp;gt; 
-				<emphasis role="italic">org.eclipse.virgo.ide.facet.core.bundlenature</emphasis> and (
-				<emphasis role="italic">com.springsource.server.ide.facet.core.parnature</emphasis> -&amp;gt; 
-				<emphasis role="italic">org.eclipse.virgo.ide.facet.core.parnature</emphasis>)). This can be changed manually (in the .project file). 
-			</para>
-			<para>The format and name of a PAR project changed. Rename 
-				<emphasis role="italic">.settings/com.springsource.server.ide.runtime.core.par.xml</emphasis> to 
-				<emphasis role="italic">.settings/org.eclipse.virgo.ide.runtime.core.par.xml</emphasis>. Inside the file rename occurences of 
-				<emphasis role="italic">com.springsource.server</emphasis> to 
-				<emphasis role="italic">org.eclipse.virgo</emphasis>. 
-			</para>
-			<para>
-				<emphasis role="bold">Snapshot build change:</emphasis> We've made a change in our tooling that will require modifying the org.eclipse.virgo.ide.runtime.core.par.xml file so that it points to the correct par.ecore URI. Rename 
-				<emphasis role="italic">xmlns:com.springsource.server.ide.par=&quot;
-					<ulink url="http:///com/springsource/server/ide/par.ecore&amp;quot">http:///com/springsource/server/ide/par.ecore&amp;quot</ulink>;
-				</emphasis> to 
-				<emphasis role="italic">&quot;xmlns:org.eclipse.virgo.ide.par=&quot;
-					<ulink url="http://eclipse.org/virgo/par.ecore&amp;quot">http://eclipse.org/virgo/par.ecore&amp;quot</ulink>;
-				</emphasis>
-			</para>
-			<para>Inside the WST settings file (
-				<emphasis role="italic">.settings/org.eclipse.wst.common.project.facet.core.xml</emphasis>) rename occurences of 
-				<emphasis role="italic">com.springsource.server.bundle</emphasis> to 
-				<emphasis role="italic">org.eclipse.virgo.server.bundle</emphasis> and occurences of 
-				<emphasis role="italic">com.springsource.server.par</emphasis> to 
-				<emphasis role="italic">org.eclipse.virgo.server.par</emphasis>. 
-			</para>
-			<para>Most/all of the conversion should be done by the following script (it has only see marginal testing, use at your own risk): 
-&lt;				pre&gt;#!/bin/sh</para>
-			<orderedlist>
-				<listitem>
-					<para>NOTE1: Run this at your own risk&amp;nbsp;:)</para>
-				</listitem>
-				<listitem>
-					<para>NOTE2: I should quote more dots in sed expressions but I'm lazy.</para>
-				</listitem>
-				<listitem>
-					<para>TODO: Delete old com.springsource files after conversion</para>
-				</listitem>
-			</orderedlist>
-			<para>if 
-				<ulink url="&amp;amp;nbsp;!">-d &amp;quot;$1&amp;quot; </ulink>; then 
-			</para>
-			<literallayout>       echo &amp;quot;Please point me at an eclipse project&amp;quot;&amp;amp;nbsp;; 
-       exit 1
-</literallayout>
-			<para>fi</para>
-			<orderedlist>
-				<listitem>
-					<para>Bundlor settings</para>
-				</listitem>
-			</orderedlist>
-			<para>f=&quot;$1/.settings/com.springsource.server.ide.bundlor.core.prefs&quot;
-				[ -f &quot;$f&quot; ] &amp;amp;&amp;amp;  (</para>
-			<literallayout>       echo &amp;quot;$1: Converting bundlor preferences&amp;quot;
-       sed -e 's/com\.springsource\.server/org.eclipse.virgo/g' &amp;quot;$f&amp;quot; &amp;amp;gt; &amp;quot;$(echo $f | sed -e s/com.springsource.server/org.eclipse.virgo/)&amp;quot;
-</literallayout>
-			<para>)</para>
-			<orderedlist>
-				<listitem>
-					<para>convert PAR</para>
-				</listitem>
-			</orderedlist>
-			<para>f=&quot;$1/.settings/com.springsource.server.ide.runtime.core.par.xml&quot;
-				[ -f &quot;$f&quot; ] &amp;amp;&amp;amp;  (</para>
-			<literallayout>       echo &amp;quot;$1: Converting PAR project dependencies&amp;quot;
-       sed -e 's/com\.springsource\.server/org.eclipse.virgo/g' &amp;quot;$f&amp;quot; &amp;amp;gt; &amp;quot;$(echo $f | sed -e s/com.springsource.server/org.eclipse.virgo/)&amp;quot;
-</literallayout>
-			<para>)</para>
-			<orderedlist>
-				<listitem>
-					<para>Fix classpaths        </para>
-				</listitem>
-			</orderedlist>
-			<para>f=&quot;$1/.classpath&quot;
-				[ -f &quot;$f&quot; ] &amp;amp;&amp;amp; (</para>
-			<literallayout>       echo &amp;quot;$1: Converting classpath containers and entries&amp;quot;
-       sed -i \
-               -e 's/com.springsource.server.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER/org.eclipse.virgo.ide.jdt.core.MANIFEST_CLASSPATH_CONTAINER/g' \
-               -e 's/com.springsource.server.ide.jdt.core.test.classpathentry/org.eclipse.virgo.ide.jdt.core.test.classpathentry/g' \
-               &amp;quot;$f&amp;quot;
-</literallayout>
-			<para>)</para>
-			<orderedlist>
-				<listitem>
-					<para>Fix natures..</para>
-				</listitem>
-			</orderedlist>
-			<para>f=&quot;$1/.project&quot;
-				[ -f &quot;$f&quot; ] &amp;amp;&amp;amp; (</para>
-			<literallayout>       echo &amp;quot;$1: Converting project natures&amp;quot;
-       sed -i \
-               -e 's/com.springsource.server.ide.facet.core.bundlenature/org.eclipse.virgo.ide.facet.core.bundlenature/g' \
-               -e 's/com.springsource.server.ide.facet.core.parnature/org.eclipse.virgo.ide.facet.core.parnature/g' \
-               &amp;quot;$f&amp;quot;
-</literallayout>
-			<para>)</para>
-			<orderedlist>
-				<listitem>
-					<para>Fix the wst file, could also replace runtime name here</para>
-				</listitem>
-			</orderedlist>
-			<para>f=&quot;$1/.settings/org.eclipse.wst.common.project.facet.core.xml&quot;
-				[ -f &quot;$f&quot; ] &amp;amp;&amp;amp; (</para>
-			<literallayout>       echo &amp;quot;$1: Converting org.eclipse.wst.common.project.facet.core.xml&amp;quot;
-       sed -i \
-               -e 's/com.springsource.server.bundle/org.eclipse.virgo.server.bundle/g'  \
-               -e 's/com.springsource.server.par/org.eclipse.virgo.server.par/g'  \
-               &amp;quot;$f&amp;quot;
-</literallayout>
-			<para>)</para>
-			<para>&lt;/pre&gt;</para>
-		</section>
-	</section>
 	<section id="Maven_plugin">
 		<title>Maven plugin</title>
 		<para>To support the development of OSGi bundles for Eclipse Virgo with Maven a Maven plugin is available. This plugin is able to start/stop a local Eclipse Virgo instance. Moreover it is possible to deploy/undeploy/refresh bundles via Maven. </para>
@@ -487,16 +319,6 @@
 		<para>We really don't recommend doing so (see 
 			<link linkend="Install_Virgo">Install_Virgo</link>). Select only Virgo Tooling and Eclipse will take care of installing anything the tooling relies on.
 		</para>
-		<itemizedlist>
-			<listitem>
-				<para>
-					<emphasis role="bold">Can I use the Virgo Tools with traditional PDE/Equinox Bundles?</emphasis>
-				</para>
-			</listitem>
-		</itemizedlist>
-		<para>Deploying PDE/Equinox Bundles to Virgo Web Server are not yet supported yet, although exporting the bundles (as Eclipse Plug-in JARs) and manually deploying to Virgo Web Server works. Please show your support on 
-			<ulink url="https://bugs.eclipse.org/bugs/show_bug.cgi?id=329198">Bugzilla #329198</ulink>.
-		</para>
 		<para>
 			<ulink url="/wiki/Category:Virgo">Category:Virgo</ulink> 
 			<ulink url="/wiki/Category:EclipseRT">Category:EclipseRT</ulink>&lt;/rev&gt;&lt;/revisions&gt;&lt;/page&gt;&lt;/pages&gt;&lt;/query&gt;&lt;/api&gt;