bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html - platform/eclipse.platform.common - Git at Google

 <!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 name="copyright" content="Copyright (c) Eclipse contributors and others 2020. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
 <meta http-equiv="Content-Language" content="en-us"/>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"/>
 <style type="text/css">
 body {max-width: 900px;}
 table.news col.title {width: 30%;}
 /*img {max-width: 520px;}*/
 table.news {table-layout: fixed; border-collapse: collapse; width: 100%;}
 table.news td {border-top: solid thin black; padding: 10px; overflow: visible;}
 table.news tr {vertical-align: top;}
 table.news tr td.section {font-size: 20px; font-weight: bold;}
 table.news tr td.title {vertical-align: top; font-weight: bold;}
 table.news tr td.content {vertical-align: top;}
 ul {padding-left: 13px;}
 </style>
 <title>What's New in 4.23 (PDE)</title>
 </head>

 <body>
 <h2>What's New in 4.23 (PDE)</h2>
 <p>Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE)
 for the 4.23 release of Eclipse. They are grouped into:</p>
 <ul> <!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
 	<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
 	<li><a href="#editors">Editors</a></li>
 	<li><a href="#APITools">API Tools</a></li>
 	<li><a href="#pde-launching">PDE Launching</a></li>
 	<!--li><a href="#pde-compiler">PDE Compiler</a></li-->
 	<!--<li><a href="#api">API Enhancements</a></li>-->
 </ul>

 	<!-- ****************** START OF N&N TABLE****************** -->
 	<table class="news">
 		<colgroup>
 			<col class="title" />
 			<col />
 		</colgroup>
 		<tbody>
 			<!-- ******************** Dialogs, Wizard and Views ********************** -->
 			<tr>
 				<td id="dialogs-wizards-views" class="section" colspan="2">
 					<h2>Dialogs, Wizards and Views</h2>
 				</td>
 			</tr>
 			<tr id="javascript">
 				<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=514294 -->
 				<td class="title"><a href="#javascript">Eclipse views with browser technology</a></td>
 				<td class="content">
 					It is possible to create views and editors with browser technology instead of SWT.
 					To showcase this, a new <b>Plug-in Template</b> is available when creating
 					a new project or a new view.
 					<p>It shows how javascript can interact with the workbench and how to run a web application
 						(a brick game) inside a view.</p>
 					<p>The views can be created using Eclipse with PDE only, but the inclusion of
 						web technology like the Wild Web Developer plug-in is recommended.</p>
 					<p>You can create a plug-in with a browser-technology-view via: <b>File &gt; New &gt; Other... &gt;
 							Plug-in Project</b>.
 					</p>
 					<p>On the last page of the wizard, you can select the template.</p>
 					<p><img src="images/brview1.png" alt="" /></p>
 					<p>Press <b>Next</b> to select the type of content you want to experiment with.</p>
 					<p><img src="images/brview2.png" alt="" /></p>
 					<p>The wizards are also accessible when you create a new view via the <b>Extensions</b> tab of the <b>Manifest
 						editor</b>.</p>
 					<p><img src="images/brview3.png" alt="" /></p>
 					<p>The <b>Workbench Interaction</b> view shows how to interact with the workbench using javascript.</p>
 					<p><img src="images/brview4.png" alt="" /></p>
 					<p>This <b>Game</b> view shows how you run a standalone web application inside a view.</p>
 					<p><img src="images/brview5.png" alt="" /></p>
 				</td>
 			</tr>

 			<tr id="context-spy">
 				<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577208 -->
 				<td class="title"><a href="#context-spy">Context Spy added to PDE</a></td>
 				<td class="content">
 				The <b>Context Spy</b> allows to view the key/values available for dependency injection.
 				This view has been migrated to PDE.
 					<p><img src="images/context-spy.png" alt="" /></p>
 				</td>
 			</tr>
 			<tr id="bundle-spy">
 				<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577207 -->
 				<td class="title"><a href="#bundle-spy">Bundle Spy added to PDE</a></td>
 				<td class="content">
 					The <b>Bundle Spy</b> allows to view the state of the OSGi bundles and is now available via PDE.
 				</td>
 			</tr>
 			<!-- ******************** End ofDialogs, Wizard and Views ********************** -->

   <!-- ******************** Editors ********************** -->
   <tr>
     <td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
   </tr>
   <tr id="pde-editor-enhancements"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=577668 -->
     <td class="title"><a href="#pde-editor-enhancements">Expand all, Collapse all button in target editor</a></td>
     <td class="content">
       It is now possible to expand all locations in the <b>Target Editor</b>.
    	  <p>
        <img src="images/pde-expand-all.png" alt="" />
       </p>
 	   If the locations are expanded, it is possible to collapse all as shown below.
        <p>
        <img src="images/pde-collapse-all.png" alt="" />
       </p>
     </td>
   </tr>
   <tr id="pde-editor-include"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=577184 -->
     <td class="title"><a href="#pde-editor-include">Reference an existing target inside another one</a></td>
     <td class="content">
       It is now possible to reference an existing target file inside another target:
    	  <p>
        <img src="images/include_target_1.png" alt="" />
       </p>
       <p>
        <img src="images/include_target_2.png" alt="" />
       </p>
       <p>
        <img src="images/include_target_3.png" alt="" />
       </p>
       This could be used for different purposes:
       <ul>
       	<li>You could use a target from a remote location (e.g. github-repository using http-protocol) in your local IDE.</li>
       	<li>You could use a target deployed at a maven repository using the mvn:&lt;groupid&gt;:&lt;artifactid&gt;:&lt;version&gt; (this requires m2eclipse with PDE integration)</li>
       	<li>You could extend an existing local target using eclipse-variables</li>
       	<li>You could combine any of the above options</li>
       </ul>
     </td>
   </tr>
   <!-- ******************** End of Editors ********************** -->

 			<!-- ******************** APITools ********************** -->
 			<tr>
 				<td id="APITools" class="section" colspan="2">
 					<h2>API Tools</h2>
 				</td>
 			</tr>

 			<tr id="reexport-removal-reported"><!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=461048 -->
 			 <td class="title"><a href="#reexport-removal-reported">Reexport removal is reported</a></td>
 			 <td class="content">
 			   If <code>visibility:=reexport</code> is removed for any required bundle, <b>API tools</b> now reports a breakage as shown below.
 			   <p>
 			    <img src="images/pde-reexport-removal.png" alt="" />
 			   </p>
 			   </td>
 			</tr>

 			<tr id="parallel-api-analysis"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=576736 -->
 			 <td class="title"><a href="#parallel-api-analysis">API analysis parallel to the build job</a></td>
 			 <td class="content">
 				To improve workflow and save time for plug-in developers, API analysis is executed now parallel to the build job.
 				This feature might sometimes not work as expected - therefore a new preference is available in the
 				<b>General &gt; Plug-in Development &gt; Run API analysis parallel to the build job</b>
 				 <p>
 			        <img src="images/api_analysis_parallel.png" alt="" />
 			    </p>
 			  </td>
 			</tr>

 			<!-- ******************** End of APITools ********************** -->

 			<!-- ******************** PDE Launching ********************** -->
 			<tr>
 				<td id="pde-launching" class="section" colspan="2">
 					<h2>PDE Launching</h2>
 				</td>
 			</tr>
 			<tr id="eclipse-applications-launching">
 			<!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=576888
 				https://bugs.eclipse.org/bugs/show_bug.cgi?id=576889
 				https://bugs.eclipse.org/bugs/show_bug.cgi?id=576890
 				https://bugs.eclipse.org/bugs/show_bug.cgi?id=351396
 				https://bugs.eclipse.org/bugs/show_bug.cgi?id=577118
 				https://bugs.eclipse.org/bugs/show_bug.cgi?id=576887
 				 -->
 				<td class="title"><a href="#eclipse-applications-launching">Improved launching of Eclipse/Equinox applications</a></td>
 				<td class="content">
 					Launching Eclipse and Equinox applications based on features has been reworked:
 					<ul>
 					 <li>To automatically add included and required features and their content</li>
 					 <li>To obey the specified version match-rules of required plug-ins and features</li>
 					 <li>To ignore included plug-ins or features if the specified environment does not match the target environment</li>
 					</ul>
 					<p>
 					 When you <b>Add Required Plug-ins</b> to a plug-in based Eclipse/Equinox application launch, 'test'-fragments are not added anymore only because their host participates in the launch.
 					 The same applies for launches based on features where requirements are added automatically.
 					 Furthermore the handling of multiple versions of bundles with the same symbolic-name has been refined for plug-in and feature based launches.
 					</p>
 				</td>
 			</tr>

 			<!-- ******************** End of PDE Launching ********************** -->

 		</tbody>
 	</table>
 <!-- ****************** END OF N&N TABLE ****************** -->

 </body>
 </html>
	<!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 name="copyright" content="Copyright (c) Eclipse contributors and others 2020. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
	<meta http-equiv="Content-Language" content="en-us"/>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"/>
	<style type="text/css">
	body {max-width: 900px;}
	table.news col.title {width: 30%;}
	/img {max-width: 520px;}/
	table.news {table-layout: fixed; border-collapse: collapse; width: 100%;}
	table.news td {border-top: solid thin black; padding: 10px; overflow: visible;}
	table.news tr {vertical-align: top;}
	table.news tr td.section {font-size: 20px; font-weight: bold;}
	table.news tr td.title {vertical-align: top; font-weight: bold;}
	table.news tr td.content {vertical-align: top;}
	ul {padding-left: 13px;}
	</style>
	<title>What's New in 4.23 (PDE)</title>
	</head>

	<body>
	<h2>What's New in 4.23 (PDE)</h2>
	<p>Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE)
	for the 4.23 release of Eclipse. They are grouped into:</p>
	<ul> <!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
	<li><a href="#dialogs-wizards-views">Dialogs, Wizards and Views</a></li>
	<li><a href="#editors">Editors</a></li>
	<li><a href="#APITools">API Tools</a></li>
	<li><a href="#pde-launching">PDE Launching</a></li>
	<!--li><a href="#pde-compiler">PDE Compiler</a></li-->
	<!--<li><a href="#api">API Enhancements</a></li>-->
	</ul>

	<!-- **************** START OF N&N TABLE**************** -->
	<table class="news">
	<colgroup>
	<col class="title" />
	<col />
	</colgroup>
	<tbody>
	<!-- ****************** Dialogs, Wizard and Views ******************** -->
	<tr>
	<td id="dialogs-wizards-views" class="section" colspan="2">
	<h2>Dialogs, Wizards and Views</h2>
	</td>
	</tr>
	<tr id="javascript">
	<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=514294 -->
	<td class="title"><a href="#javascript">Eclipse views with browser technology</a></td>
	<td class="content">
	It is possible to create views and editors with browser technology instead of SWT.
	To showcase this, a new <b>Plug-in Template</b> is available when creating
	a new project or a new view.
	<p>It shows how javascript can interact with the workbench and how to run a web application
	(a brick game) inside a view.</p>
	<p>The views can be created using Eclipse with PDE only, but the inclusion of
	web technology like the Wild Web Developer plug-in is recommended.</p>
	<p>You can create a plug-in with a browser-technology-view via: <b>File > New > Other... >
	Plug-in Project</b>.
	</p>
	<p>On the last page of the wizard, you can select the template.</p>
	<p><img src="images/brview1.png" alt="" /></p>
	<p>Press <b>Next</b> to select the type of content you want to experiment with.</p>
	<p><img src="images/brview2.png" alt="" /></p>
	<p>The wizards are also accessible when you create a new view via the <b>Extensions</b> tab of the <b>Manifest
	editor</b>.</p>
	<p><img src="images/brview3.png" alt="" /></p>
	<p>The <b>Workbench Interaction</b> view shows how to interact with the workbench using javascript.</p>
	<p><img src="images/brview4.png" alt="" /></p>
	<p>This <b>Game</b> view shows how you run a standalone web application inside a view.</p>
	<p><img src="images/brview5.png" alt="" /></p>
	</td>
	</tr>

	<tr id="context-spy">
	<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577208 -->
	<td class="title"><a href="#context-spy">Context Spy added to PDE</a></td>
	<td class="content">
	The <b>Context Spy</b> allows to view the key/values available for dependency injection.
	This view has been migrated to PDE.
	<p><img src="images/context-spy.png" alt="" /></p>
	</td>
	</tr>
	<tr id="bundle-spy">
	<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577207 -->
	<td class="title"><a href="#bundle-spy">Bundle Spy added to PDE</a></td>
	<td class="content">
	The <b>Bundle Spy</b> allows to view the state of the OSGi bundles and is now available via PDE.
	</td>
	</tr>
	<!-- ****************** End ofDialogs, Wizard and Views ******************** -->

	<!-- ****************** Editors ******************** -->
	<tr>
	<td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
	</tr>
	<tr id="pde-editor-enhancements"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=577668 -->
	<td class="title"><a href="#pde-editor-enhancements">Expand all, Collapse all button in target editor</a></td>
	<td class="content">
	It is now possible to expand all locations in the <b>Target Editor</b>.
	<p>
	<img src="images/pde-expand-all.png" alt="" />
	</p>
	If the locations are expanded, it is possible to collapse all as shown below.
	<p>
	<img src="images/pde-collapse-all.png" alt="" />
	</p>
	</td>
	</tr>
	<tr id="pde-editor-include"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=577184 -->
	<td class="title"><a href="#pde-editor-include">Reference an existing target inside another one</a></td>
	<td class="content">
	It is now possible to reference an existing target file inside another target:
	<p>
	<img src="images/include_target_1.png" alt="" />
	</p>
	<p>
	<img src="images/include_target_2.png" alt="" />
	</p>
	<p>
	<img src="images/include_target_3.png" alt="" />
	</p>
	This could be used for different purposes:
	<ul>
	<li>You could use a target from a remote location (e.g. github-repository using http-protocol) in your local IDE.</li>
	<li>You could use a target deployed at a maven repository using the mvn:<groupid>:<artifactid>:<version> (this requires m2eclipse with PDE integration)</li>
	<li>You could extend an existing local target using eclipse-variables</li>
	<li>You could combine any of the above options</li>
	</ul>
	</td>
	</tr>
	<!-- ****************** End of Editors ******************** -->

	<!-- ****************** APITools ******************** -->
	<tr>
	<td id="APITools" class="section" colspan="2">
	<h2>API Tools</h2>
	</td>
	</tr>

	<tr id="reexport-removal-reported"><!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=461048 -->
	<td class="title"><a href="#reexport-removal-reported">Reexport removal is reported</a></td>
	<td class="content">
	If <code>visibility:=reexport</code> is removed for any required bundle, <b>API tools</b> now reports a breakage as shown below.
	<p>
	<img src="images/pde-reexport-removal.png" alt="" />
	</p>
	</td>
	</tr>

	<tr id="parallel-api-analysis"> <!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=576736 -->
	<td class="title"><a href="#parallel-api-analysis">API analysis parallel to the build job</a></td>
	<td class="content">
	To improve workflow and save time for plug-in developers, API analysis is executed now parallel to the build job.
	This feature might sometimes not work as expected - therefore a new preference is available in the
	<b>General > Plug-in Development > Run API analysis parallel to the build job</b>
	<p>
	<img src="images/api_analysis_parallel.png" alt="" />
	</p>
	</td>
	</tr>

	<!-- ****************** End of APITools ******************** -->

	<!-- ****************** PDE Launching ******************** -->
	<tr>
	<td id="pde-launching" class="section" colspan="2">
	<h2>PDE Launching</h2>
	</td>
	</tr>
	<tr id="eclipse-applications-launching">
	<!--https://bugs.eclipse.org/bugs/show_bug.cgi?id=576888
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=576889
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=576890
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=351396
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=577118
	https://bugs.eclipse.org/bugs/show_bug.cgi?id=576887
	-->
	<td class="title"><a href="#eclipse-applications-launching">Improved launching of Eclipse/Equinox applications</a></td>
	<td class="content">
	Launching Eclipse and Equinox applications based on features has been reworked:
	<ul>
	<li>To automatically add included and required features and their content</li>
	<li>To obey the specified version match-rules of required plug-ins and features</li>
	<li>To ignore included plug-ins or features if the specified environment does not match the target environment</li>
	</ul>
	<p>
	When you <b>Add Required Plug-ins</b> to a plug-in based Eclipse/Equinox application launch, 'test'-fragments are not added anymore only because their host participates in the launch.
	The same applies for launches based on features where requirements are added automatically.
	Furthermore the handling of multiple versions of bundles with the same symbolic-name has been refined for plug-in and feature based launches.
	</p>
	</td>
	</tr>

	<!-- ****************** End of PDE Launching ******************** -->

	</tbody>
	</table>
	<!-- **************** END OF N&N TABLE **************** -->

	</body>
	</html>