pde-ui/nan/3.6/M6/pde-3.6M6.html - www.eclipse.org/pde - Git at Google

 <?xml version="1.0" encoding="iso-8859-1"?>
 <!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-Language" content="en-us" />
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
 <title>Eclipse "New and Noteworthy" Template</title>
 </head><body>
 <h1>Eclipse "New and Noteworthy" Template</h1>
 <p>Last revised October 29, 2007</p>
 <p>This is the template for the "New and Noteworthy" document that
   accompanies each Eclipse project milestone build.</p>
 <p>Note: This template document is XHTML 1.0 Transitional. Please use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
     Markup Validation Service</a> to check your document's markup before submitting.
     This will detect screwed up HTML tags, images without an "alt"
   attrribute, and other tedious little details. </p>
 <table border="0" cellpadding="10" cellspacing="0" width="80%">
 <tbody>
 <tr>
 <td colspan="2">
 <hr/>
 <h2>PDE
 </h2>
 <hr/></td>
 </tr>
 <tr id="featurelaunch">
 <td align="left" valign="top" width="30%"><b>Feature based launch
 </b></td>
 <td valign="top" width="70%">You can now manage the set of bundles launched
 in an Eclipse Application by selecting a set of features. PDE automatically
 launches all of the bundles in the selected features along with all of their required bundles.
 On the <b>Plug-ins</b> tab, choose '<b>features selected below</b>' to display
 and select features to launch.
 <p><img alt="Feature Based Launching" title="Feature Based Launching"
 src="images/feature-launch.png"/><br/><br/></p>
 <p>
  Features in the workspace are used over external features - however, this
 can be configured by un-checking '<b>Use features from workspace if available</b>'.
 Bundles in the workspace are used over external bundles in the
 target platform. However, this can be configured by modifying the configuration's
 default bundle resolution policy, or can be configured per feature using the
 cell editors in the '<b>Plug-in Location</b>' column.
 </p>
 </td>
 </tr>
 <tr>
 <td colspan="2">
 <hr/> </td>
 </tr>
 <tr id="featuretarget">
 <td align="left" valign="top" width="30%"><b>Feature based target
 </b></td>
 <td valign="top" width="70%">You can now manage the set of bundles in a target
 platform by selecting a set of features. Additionally, you can select from
 bundles that are not contained in any feature. On a target definition's
 <b>Content</b> tab select the <b>Manage using Features</b> radio button. This
 provides coarse grained management of bundles in a target. When a feature
 is selected, all bundles in that feature are added to the target.
 <p><img alt="Target Based Features" title="Target Based Features"
 src="images/target-features.png"/><br/><br/></p>
 </td>
 </tr>
 <tr>
 <td colspan="2">
 <hr/> </td>
 </tr>
 <tr id="apireports">
 <td align="left" valign="top" width="30%"><b>Customize API use scan reports
 </b></td>
 <td valign="top" width="70%">A new wizard helps you customize API use reports.
 From the <b>Patterns</b> tab of an <b>API Use Report</b> launch configuration
 (available via External Tools), press the <b>Add</b> button to open the wizard
 and create custom pattern filters.
 <p><img alt="API Pattern Wizard" title="API Pattern Wizard"
 src="images/api-filters.png"/><br/><br/></p>
 <p>
 An <b>Archive Pattern</b> allows specific jars within
 bundles to be omitted from the scan. A <b>Package Pattern</b> allows you to
 specify which packages should be considered API or non-API (override visibility
 definitions in bundle manifests). A <b>Report Conversion Pattern</b> allows
 specific references to be filtered from the final report. You can filter
 references from or to locations based on regular expressions.
 </p>
 </td>
 </tr>

 <td colspan="2">
 <hr/> </td>

 <tr id="pdetargetdialog">
 <td align="left" valign="top" width="30%"><b>Add to Target Platform Dialog</b>
 </b></td>
 <td valign="top" width="70%">The <b>Add Artifact to Target Platform</b> dialog (Ctrl+Shift+Alt+A) allows you to quickly search a set of repositories for dependencies (bundle, feature or package) to add to your current target platform.
 <p><img alt="Add Artifact to Target Platform Dialog" title="Add Artifact to Target Platform Dialog"
 src="images/add-to-target.png"/><br/><br/></p>
 </td>
 </tr>

 <tr id="pdetargetdialog">
 <td align="left" valign="top" width="30%"><b>Search Repositories Quickfix</b>
 </b></td>
 <td valign="top" width="70%">A new quickfix allows you to conveniently search a set of repositories for a missing imported package and have a bundle supplying the package added to your target platform.
 <p><img alt="Search Repositories Quickfix" title="Search Repositories Quickfix"
 src="images/hover-quick-fix.png"/><br/><br/></p>
 </td>
 </tr>

 </tbody>
 </table>
 </body></html>
	<?xml version="1.0" encoding="iso-8859-1"?>
	<!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-Language" content="en-us" />
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
	<title>Eclipse "New and Noteworthy" Template</title>
	</head><body>
	<h1>Eclipse "New and Noteworthy" Template</h1>
	<p>Last revised October 29, 2007</p>
	<p>This is the template for the "New and Noteworthy" document that
	accompanies each Eclipse project milestone build.</p>
	<p>Note: This template document is XHTML 1.0 Transitional. Please use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
	Markup Validation Service</a> to check your document's markup before submitting.
	This will detect screwed up HTML tags, images without an "alt"
	attrribute, and other tedious little details. </p>
	<table border="0" cellpadding="10" cellspacing="0" width="80%">
	<tbody>
	<tr>
	<td colspan="2">
	<hr/>
	<h2>PDE
	</h2>
	<hr/></td>
	</tr>
	<tr id="featurelaunch">
	<td align="left" valign="top" width="30%"><b>Feature based launch
	</b></td>
	<td valign="top" width="70%">You can now manage the set of bundles launched
	in an Eclipse Application by selecting a set of features. PDE automatically
	launches all of the bundles in the selected features along with all of their required bundles.
	On the <b>Plug-ins</b> tab, choose '<b>features selected below</b>' to display
	and select features to launch.
	<p><img alt="Feature Based Launching" title="Feature Based Launching"
	src="images/feature-launch.png"/><br/><br/></p>
	<p>
	Features in the workspace are used over external features - however, this
	can be configured by un-checking '<b>Use features from workspace if available</b>'.
	Bundles in the workspace are used over external bundles in the
	target platform. However, this can be configured by modifying the configuration's
	default bundle resolution policy, or can be configured per feature using the
	cell editors in the '<b>Plug-in Location</b>' column.
	</p>
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr/> </td>
	</tr>
	<tr id="featuretarget">
	<td align="left" valign="top" width="30%"><b>Feature based target
	</b></td>
	<td valign="top" width="70%">You can now manage the set of bundles in a target
	platform by selecting a set of features. Additionally, you can select from
	bundles that are not contained in any feature. On a target definition's
	<b>Content</b> tab select the <b>Manage using Features</b> radio button. This
	provides coarse grained management of bundles in a target. When a feature
	is selected, all bundles in that feature are added to the target.
	<p><img alt="Target Based Features" title="Target Based Features"
	src="images/target-features.png"/><br/><br/></p>
	</td>
	</tr>
	<tr>
	<td colspan="2">
	<hr/> </td>
	</tr>
	<tr id="apireports">
	<td align="left" valign="top" width="30%"><b>Customize API use scan reports
	</b></td>
	<td valign="top" width="70%">A new wizard helps you customize API use reports.
	From the <b>Patterns</b> tab of an <b>API Use Report</b> launch configuration
	(available via External Tools), press the <b>Add</b> button to open the wizard
	and create custom pattern filters.
	<p><img alt="API Pattern Wizard" title="API Pattern Wizard"
	src="images/api-filters.png"/><br/><br/></p>
	<p>
	An <b>Archive Pattern</b> allows specific jars within
	bundles to be omitted from the scan. A <b>Package Pattern</b> allows you to
	specify which packages should be considered API or non-API (override visibility
	definitions in bundle manifests). A <b>Report Conversion Pattern</b> allows
	specific references to be filtered from the final report. You can filter
	references from or to locations based on regular expressions.
	</p>
	</td>
	</tr>

	<td colspan="2">
	<hr/> </td>

	<tr id="pdetargetdialog">
	<td align="left" valign="top" width="30%"><b>Add to Target Platform Dialog</b>
	</b></td>
	<td valign="top" width="70%">The <b>Add Artifact to Target Platform</b> dialog (Ctrl+Shift+Alt+A) allows you to quickly search a set of repositories for dependencies (bundle, feature or package) to add to your current target platform.
	<p><img alt="Add Artifact to Target Platform Dialog" title="Add Artifact to Target Platform Dialog"
	src="images/add-to-target.png"/><br/><br/></p>
	</td>
	</tr>

	<tr id="pdetargetdialog">
	<td align="left" valign="top" width="30%"><b>Search Repositories Quickfix</b>
	</b></td>
	<td valign="top" width="70%">A new quickfix allows you to conveniently search a set of repositories for a missing imported package and have a bundle supplying the package added to your target platform.
	<p><img alt="Search Repositories Quickfix" title="Search Repositories Quickfix"
	src="images/hover-quick-fix.png"/><br/><br/></p>
	</td>
	</tr>

	</tbody>
	</table>
	</body></html>