/
platform_whatsnew.html
185 lines (176 loc) · 9.82 KB
/
platform_whatsnew.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
<!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 section in the documentation 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">
/*<![CDATA[*/
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>Eclipse Platform What's New in 4.30</title>
</head>
<body>
<h2>What's New in Eclipse 4.30 (Platform)</h2>
<p>Here are descriptions of some of the more interesting or significant changes made to the Eclipse Platform for the
4.30 release of Eclipse. They are grouped into:</p>
<ul>
<!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
<!--li><a href="#ViewsAndDialogs">Views, Dialogs and Toolbar</a></li-->
<!--li><a href="#TextEditors">Text Editors</a></li-->
<!--li><a href="#Preferences">Preferences</a></li-->
<!--li><a href="#Debug">Debug</a></li-->
<!--li><a href="#StylingThemes">Themes and Styling</a></li-->
<li><a href="#Security">Security</a></li>
<li><a href="#GeneralUpdates">General Updates</a></li>
</ul>
<p>Plug-in developers will also be interested in the corresponding <a href=
"../../org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.html">What's new</a> document in the plug-in
developer's guide.</p>
<p>We also recommend to read the <a href="../tips/platform_tips.html">Tips and Tricks</a>.</p><br />
<!-- ****************** START OF N&N TABLE ****************** -->
<table class="news">
<colgroup>
<col class="title" />
<col />
</colgroup>
<tbody>
<!-- ******************* Views, Dialogs and Toolbar ************************************* -->
<!--tr>
<td id="ViewsAndDialogs" class="section" colspan="2">
<h2>Views, Dialogs and Toolbar </h2>
</td>
</tr-->
<!-- ******************* End of Views, Dialogs and Toolbar ************************************* -->
<!-- ******************* Text Editors ************************************* -->
<!--tr>
<td id="TextEditors" class="section" colspan="2">
<h2>Text Editors </h2>
</td>
</tr-->
<!-- ******************* End of Text Editors ************************************* -->
<!-- ****************** Preferences ************************************* -->
<!--tr>
<td id="Preferences" class="section" colspan="2">
<h2>Preferences </h2>
</td>
</tr-->
<!-- ****************** End of Preferences ************************************* -->
<!-- ******************* Themes and Styling ************************************* -->
<!--tr>
<td id="StylingThemes" class="section" colspan="2">
<h2>Themes and Styling </h2>
</td>
</tr-->
<!-- ******************* End of Themes and Styling ************************************* -->
<!-- ******************* Security ************************************* -->
<tr>
<td id="Security" class="section" colspan="2">
<h2>Security</h2>
</td>
</tr>
<tr id="p2-director">
<!-- https://github.com/eclipse-equinox/p2/issues/365 -->
<td class="title">p2 Director Application Security</td>
<td class="content">
To provide similar security controls as <a href="https://eclipse.dev/eclipse/news/4.28/platform.php#Security" target="_blank">available in the IDE</a>,
the following command-line arguments are now supported the <a href="https://help.eclipse.org/latest/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_director.html" target="_blank">p2 director application</a>:
<p></p>
<dl>
<dt>-trustSignedContentOnly | -tsco</dt>
<dd>
Whether to trust each artifact only if it is jar-signed or PGP-signed.
</dd>
<dt>-trustedAuthorities | -ta <comma separated list></dt>
<dd>
The authorities from which repository content, including repository metadata, is trusted. An empty value will reject all remote connections.
</dd>
<dt>-trustedPGPKeys | -tk <comma separated list></dt>
<dd>
The fingerprints of PGP keys to trust as signers of artifacts. An empty value will reject all PGP keys.
</dd>
<dt>-trustedCertificates | -tc <comma separated list></dt>
<dd>
The SHA-256 'fingerprints' of unanchored certificates to trust as signers of artifacts. An empty value will reject all unanchored certificates.
</dd>
<dt>-verboseTrust | -vt</dt>
<dd>
Whether to print detailed information about the content trust.
</dd>
</dl>
</td>
</tr>
<!-- ******************* End of Security ************************************* -->
<!-- ******************* General Updates ************************************* -->
<tr>
<td id="GeneralUpdates" class="section" colspan="2">
<h2>General Updates </h2>
</td>
</tr>
<tr id="support-jakarta-annotations">
<!-- https://github.com/eclipse-platform/eclipse.platform/pull/696 -->
<!-- https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/1056 -->
<td class="title">Support for Jakarta Annotations by Eclipse E4</td>
<td class="content">
The Eclipse E4 Platform Dependency Injector now supports annotations from the <code>jakarta.inject</code> and <code>jakarta.annotation</code> package.
<p>
Plug-in developers are encouraged to migrate their E4 application model element classes to use for example <code>jakarta.inject.Inject</code> instead of <code>javax.inject.Inject</code>
or <code>jakarta.annotation.PostConstruct</code> instead of <code>javax.annotation.PostConstruct</code>.
At the moment annotations from both namespaces <code>jakarta</code> and <code>javax</code> are supported.
</p>
<p>
The support for annotations from the <code>javax.inject</code> and <code>javax.annotation</code> package is now deprecated and will be removed in a future release, after a deprecation period of at least two years.
If it necessary to make a Plug-in compatible with past versions (that don't support <code>jakarta</code> annotations), recent and future versions (that don't support <code>javax</code> annotations) of the E4-Injector,
it can be considered to apply the annotations from both namespaces simultaneously and to import the packages from both namespaces only optionally.
But this strategy does not work for usages of the <code>javax/jakarta.inject.Provider</code> and should generally be used with caution and be verified in detail for more complex setups.
</p>
<p>
The Eclipse SDK itself already has been migrated off these annotations from the <code>javax</code> namespace to the <code>jakarta</code> replacements and therefore does not pull the former into a target-platform anymore.
If your application still needs these <code>javax</code> annotations you potentially have to add them explicitly to your target using entries like:
</p>
<pre><code>
<unit id="jakarta.inject.jakarta.inject-api" version="1.0.5"/>
<unit id="jakarta.annotation-api" version="1.3.5"/>
</code></pre>
<p>
Counterintuitively the <code>javax</code> annotations are provided by a bundle with the same symbolic name as their <code>jakarta</code> successor but with a 1.x version, while the jakarta successors have a 2.x version.
It is therefore necessary to specify the version explicitly since those bundles are not required in their latest version.
</p>
</td>
</tr>
<tr id="new-ecf-client">
<!-- https://github.com/eclipse-equinox/p2/pull/206 -->
<td class="title"><a href="#new-ecf-client">New Http Client Backend for P2</a></td>
<td class="content">
<p>The ECF Backend used by P2 has switched to use the httpjava-client to lower the dependency chain and efforts to maintain certain third party libraries.</p>
<p>
For now Eclipse will ship both, the new and the old backend while the newer one takes precedence. If you see any issues please proceed as follows:
<ol>
<li>Collect as much data as possible, e.g. is a proxy used, are the site you want contact password protected, your os and similar what could be useful or is know to diverge from standard desktop environment settings.</li>
<li><a href="https://github.com/eclipse-equinox/p2/issues?q=is%3Aissue+is%3Aopen+label%3A%22ecf+transport%22" target="_blank">Open an issue here</a> with the description of the problem and the collected data.</li>
<li>Consider <a href="https://github.com/eclipse-equinox/p2/blob/master/CONTRIBUTING" target="_blank">providing a test-case for P2</a> to make sure your use-case is covered now and in the future and will not break again</li>
<li>Configure your <code>eclipse.ini</code> to include <code>-Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclientjava</code> unless the problem is fixed</li>
</ol>
</p>
</td>
</tr>
<!-- ******************* End of General Updates ************************************* -->
<tr><td colspan="2"/></tr>
</tbody>
</table>
<!-- ****************** END OF N&N TABLE ****************** -->
</body>
</html>