Skip to content

Commit

Permalink
NN4.24 (#22)
Browse files Browse the repository at this point in the history
* N&N for 4.24

Copy content from news repo to doc bundle. Update topics*.xml
Add target=_blank to links, add missing anchor tags

fixes eclipse-platform/eclipse.platform.common#21
  • Loading branch information
lshanmug committed May 25, 2022
1 parent 3ef8357 commit 30dfaaf
Show file tree
Hide file tree
Showing 63 changed files with 422 additions and 458 deletions.
4 changes: 2 additions & 2 deletions bundles/org.eclipse.jdt.doc.user/topics_WhatsNew.xml
Expand Up @@ -4,8 +4,8 @@
<!-- Define topics for the What's New -->
<!-- ================================ -->
<toc label="What's New">
<topic href="whatsNew/jdt_whatsnew.html#Java18" label="Java 18 Support"/>
<topic href="whatsNew/jdt_whatsnew.html#JUnit" label="JUnit"/>
<topic href="whatsNew/jdt_whatsnew.html#JavaEditor" label="Java Editor"/>
<topic href="whatsNew/jdt_whatsnew.html#JavaViewsandDialogs" label="Java Views and Dialogs"/>
<topic href="whatsNew/jdt_whatsnew.html#JavaFormatter" label="Java Formatter"/>
<topic href="whatsNew/jdt_whatsnew.html#Debug" label="Debug"/>
</toc>
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
237 changes: 119 additions & 118 deletions bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html

Large diffs are not rendered by default.

2 changes: 0 additions & 2 deletions bundles/org.eclipse.pde.doc.user/topics_WhatsNew.xml
Expand Up @@ -17,6 +17,4 @@
<toc label="What's new">
<topic href="whatsNew/pde_whatsnew.html#dialogs-wizards-views" label="Dialog, Wizards and Views"/>
<topic href="whatsNew/pde_whatsnew.html#editors" label="Editors"/>
<topic href="whatsNew/pde_whatsnew.html#APITools" label="API Tools"/>
<topic href="whatsNew/pde_whatsnew.html#pde-launching" label="PDE Launching"/>
</toc>
Binary file not shown.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
Diff not rendered.
246 changes: 91 additions & 155 deletions bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html
Expand Up @@ -17,187 +17,123 @@
table.news tr td.content {vertical-align: top;}
ul {padding-left: 13px;}
</style>
<title>What's New in 4.23 (PDE)</title>
<title>What's New in 4.24 (PDE)</title>
</head>

<body>
<h2>What's New in 4.23 (PDE)</h2>
<h2>What's New in 4.24 (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>
for the 4.24 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="#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 ********************** -->
<!-- ****************** START OF N&N TABLE****************** -->
<table class="news">
<colgroup>
<col class="title" />
<col />
</colgroup>
<tbody>
<!-- ******************** Dialogs, Wizard and Views ********************** -->
<tr>
<td id="editors" class="section" colspan="2"><h2>Editors</h2></td>
<td id="dialogs-wizards-views" class="section" colspan="2"><h2>Dialogs, Wizards and Views</h2></td>
</tr>
<tr id="event-spy">
<!-- https://github.com/eclipse-pde/eclipse.pde/issues/85 -->
<td class="title"><a href="#bundle-spy">Event Spy added to PDE</a></td>
<td class="content">
<p> The <b>Event Spy</b> allows to view the events sent using an <code>IEventBroker</code> and is now available via PDE, using the <b>Spies</b> menu or the <b>Alt+Shift+F8</b> shortcut (on windows). </p>
<img src="images/eventSpyMenuAndShortcut.png" alt="" />
<p>Start capturing events, and check the event's contents in the table. For instance, here the spy window has moved, and all the location events were caught.</p>
<img src="images/eventSpyInPde.png" alt="" />
</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>

<tr id="auto-add-requirements-launches">
<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544838 -->
<td class="title"><a href="#auto-add-requirements-launches">Include requirements automatically when launching an application</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="" />
The <b>Launch Configuration</b> Wizard offers a new option in the <b>Plug-ins</b> tab to include required but missing plug-ins or features automatically while launching an Eclipse or Equinox application.
By default this is enabled for Launch Configurations based on Features and disabled for those based on products, which reflects the previous behavior.
<p>
Missing plug-ins/features are only added to the launched application but not to the Launch Configuration.
This allows to specify only the 'root' features/plug-ins you actually want in your application and to let Eclipse include only the minimal set of requirements in each launch.
Consequently new dependencies don't have to be added to the Launch Configuration anymore.
</p>
<p><img src="images/autoIncludeLaunch.png" alt="Automatically include requirements in launch"/></p>
</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-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>
<tr id="auto-add-requirements-products">
<!--
https://bugs.eclipse.org/bugs/show_bug.cgi?id=570760
https://github.com/eclipse-pde/eclipse.pde/pull/7
-->
<td class="title"><a href="#auto-add-requirements-products">Include requirements automatically when launching a product</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>
The <b>Product Editor</b> offers a new option in the <b>Contents</b> tab to include required but missing features or plug-ins automatically when launching the product from the IDE.
<p>
<img src="images/include_target_3.png" alt="" />
This controls if the corresponding option, which is described above, is activated or not for the Launch Configuration associated with the product launch.
By default this option is enabled for Feature and Plug-in based products to behave the same like when the product is build with <b>Eclipse Tycho</b>.
</p>
This could be used for different purposes:
<p><img src="images/autoIncludeProduct.png" alt="Automatically include requirements in product"/></p>
</td>
</tr>

<tr id="launching-alignment">
<!--
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340350
https://github.com/eclipse-pde/eclipse.pde/pull/107
https://bugs.eclipse.org/bugs/show_bug.cgi?id=578644
-->
<td class="title"><a href="#launching-alignment">Products launched from IDE now better behave like products built with Maven/Tycho</a></td>
<td class="content">
Launching a Product from within the IDE via the <b>Product Editor</b> has been improved in the following aspects to result in an application whose set of plug-ins/features is as close as possible to what is assembled when the product is build by <b>Maven</b> and <b>Eclipse Tycho</b>:
<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>
<li>Launching a product based on features creates a feature-based Launch Configuration</li>
<li>Missing requirements are included by default (as described above)</li>
<li>When launching a plugin-based product optional requirements are ignored by default when computing missing requirements</li>
<li>When automatically including requirements, fragments are not added just because their host-plug-in is included</li>
</ul>
Together with the <a href="https://www.eclipse.org/eclipse/news/4.23/pde.php#eclipse-applications-launching" target="_blank">Improved launching of Eclipse/Equinox applications</a> in the previous release Eclipse 2022-03 it is now much simpler to set up products.
As an example, to create the Eclipse SDK as a Product you only have to create a Product with basic settings via the Wizard, configure it to use features and add the <code>org.eclipse.sdk</code> feature.
The Product is ready to launch.
If you want Git support, just add the <code>org.eclipse.egit</code> feature and in case you want to develop Maven projects in your Product, just add <code>org.eclipse.m2e.feature</code>.
</td>
</tr>
</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>
<!-- ******************** APITools ********************** -->
<!--
<tr>
<td id="APITools" class="section" colspan="2"><h2>API Tools</h2></td>
</tr>
-->
<!-- ******************** End of APITools ********************** -->

<!-- ******************** 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>
<!-- ******************** PDE Compiler ********************** -->
<!--
<tr>
<td id="pde-compiler" class="section" colspan="2"><h2>PDE Compiler</h2></td>
</tr>
-->
<!-- ******************** End of PDE Compiler ********************** -->
<tr><td colspan="2"/></tr>
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->

</body>
Expand Down
1 change: 0 additions & 1 deletion bundles/org.eclipse.platform.doc.isv/topics_WhatsNew.xml
Expand Up @@ -6,5 +6,4 @@
<toc label="What's new">
<topic href="whatsNew/platform_isv_whatsnew.html#Platform" label="Platform"/>
<topic href="whatsNew/platform_isv_whatsnew.html#SWT" label="SWT"/>
<topic href="whatsNew/platform_isv_whatsnew.html#Equinox" label="Equinox"/>
</toc>
Diff not rendered.
Diff not rendered.

0 comments on commit 30dfaaf

Please sign in to comment.