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
186
187
188
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2012. 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=ISO-8859-1"/>
<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
<style type="text/css">
table.news td {border-top: solid thin black;}
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; width: 30%; font-weight: bold;}
table.news tr td.content {vertical-align: top; width: 70%;}
</style>
<title>Eclipse Juno - New and Noteworthy</title>
</head>
<body>
<div style="font-size: 20px; font-weight: bold;">Plug-in Development Environment</div>
<!-- ****************** START OF N&N TABLE ****************** -->
<table class="news" cellpadding="10" cellspacing="0">
<!-- ******************* Views/Editors ******************** -->
<tr>
<td id="ViewsAndEditors" class="section" colspan="2">
<h2>
Views and editors
</h2>
</td>
</tr>
<tr id="vendor-history">
<td class="title">Plug-in vendor history</td>
<td class="content">
When creating a new plug-in, fragment or feature the Vendor information used in the creation wizard is retained and can be reused
by selecting the drop-down in subsequent uses of the wizard.
<p>
<img src="images/pde-wizard.png" alt="The Vendor history drop-down"/>
</p>
</td>
</tr>
<tr id="pde-import-package-explorer">
<td class="title">Import from repository in the Package Explorer view</td>
<td class="content">
By using <b>File > Import... > Import Plug-ins and Fragments</b> you can import the source
code for a plug-in from your installation if the plug-in has the necessary manifest header.
Now you can access this functionality directly from the Package Explorer and Project Explorer
views. Right click on a plug-in in your project's <b>Plug-in Dependencies</b> classpath container
and select <b>Import from Repository...</b>.
<p><img src="images/import-repo-pkg.png" alt="Import from repository in package explorer view"/></p>
<p>Importing from a repository is also available in the Target Platform State, Plug-in Dependencies and Plug-ins
views. If the selected item can be imported, there will be an <b>Import As</b> menu visible when right clicking in
the view.</p>
<p><img src="images/import-repo-tps.png" alt="Import from repository in target platform state view"/></p>
</td>
</tr>
<tr id="TracingPage">
<td class="title">Tracing preference page</td>
<td class="content">
A new preference page is available to dynamically set the debug tracing options for Eclipse. You can turn on individual tracing options and the changes will take effect immediately. There is no need to restart Eclipse.
<p><img src="images/tracing_page.png" alt="Tracing preference page"/></p>
<p>To add a plug-in's tracing options to the page, you must provide an <code>org.eclipse.ui.trace.traceComponents</code> extension. Your bundle must also register an <code>org.eclipse.osgi.service.debug.DebugOptionsListener</code> to be notified when tracing options are changed.</p>
<p>The preference page can be included in other products. It is contained in the <code>org.eclipse.ui.trace</code> plug-in and has no dependencies on PDE.</p>
</td>
</tr>
<tr id="product-add-required">
<td class="title">Add required in feature based product</td>
<td class="content">
The product editor now has an <b>Add Required</b> button when editing a feature based product. Pressing the button will add all the features that are required by the features already in the product configuration.
<p><img src="images/addrequired.png" alt="Add required button"/></p>
</td>
</tr>
<tr id="extensions-editor-enhancements">
<td class="title">Extension editor enhancements</td>
<td class="content">
Several improvements have been made to the extensions tab of the <b>Plug-in Editor</b>.
<p><img src="images/extensions_page.png" alt="Extensions editor enhancements"/></p>
<ul>
<li><b>Filter related:</b> Available by right clicking and pressing <b>Filter Related</b>, only extensions that are related (same id, label, class, etc) will be displayed in the tree</li>
<li><b>Filter enhancements:</b> The standard filter textbox now supports multiple filters separated by "/", matches are bolded, and the filter applies to extension attributes</li>
<li><b>Label improvements:</b> More items will display icons and labels, class names are displayed without package name</li>
<li><b>Accelerated scrolling:</b> Pressing <b>Ctrl</b> while scrolling does fast scrolling</li>
<li><b>Better expansion:</b> The expand state of selected items can be toggled with a new action</li>
</ul>
</td>
</tr>
<tr id="workspace-deletion-cancel">
<td class="title">Workspace deletion is cancelable</td>
<td class="content">
Eclipse and OSGi launch configurations have the option to delete the workspace and configuration folders before launching. This can be a long running operation with large workspaces. The operation is now cancelable which will stop the launch.
</td>
</tr>
<!-- ***************** Target Platform ******************* -->
<tr>
<td id="TargetPlatform" class="section" colspan="2">
<h2>
Target Platform
</h2>
</td>
</tr>
<tr id="custom-target-locations">
<td class="title">Custom target locations</td>
<td class="content">
You can now provide custom locations for target definitions. They appear in both the target
definition editor and wizard along with the platform provided target locations: directory, installation,
feature and software site.
<p>To provide a custom location, you must implement <tt>ITargetLocation</tt> and extend the extension point
<tt>org.eclipse.pde.core.targetLocations</tt>. To provide labels, wizards and other user interface elements,
you must extend an additional extension point <tt>org.eclipse.pde.ui.targetLocationProvisioners</tt> and have
your <tt>ITargetLocation</tt> implementation adapt to several types. For additional details, view the Javadoc on
<tt>ITargetLocation</tt>.</p>
</td>
</tr>
<tr id="pde-classpath-api">
<td class="title">Bundle classpath resolution API</td>
<td class="content">
The <b>org.eclipse.pde.core.bundleClasspathResolvers</b> extension point allows
you to dynamically add additional content to the runtime classpath and source
lookup path of workspace plug-ins at launch time.
</td>
</tr>
<tr id="NonJarTargetPlugins">
<td class="title">Non *.jar plug-ins in target platform</td>
<td class="content">
The target platform will now recognize archive files with any file extension as long as they contain a manifest with the necessary OSGi headers. Previously, PDE only supported directory plug-ins and jarred (*.jar) plug-ins.
</td>
</tr>
<tr id="target-configure-phase">
<td class="title">Target definition configure phase</td>
<td class="content">
When working with a target definition containing a software site location (such as a p2 repository) it is now possible to change whether the p2 configuration phase should be run when resolving the target. By default the configuration phase is not included. Changing the setting will change all locations in the target definition.
<p><img src="images/configurephase.png" alt="Configure phase option"/></p>
</td>
</tr>
<!-- ******************** API Tools ********************** -->
<tr>
<td id="APITools" class="section" colspan="2">
<h2>
API Tools
</h2>
</td>
</tr>
<tr id="api-tracing">
<td class="title">API Tools tracing</td>
<td class="content">
API Tools has added all debug tracing settings to the <b>Tracing</b> preference page where they can be enabled and disabled as needed without restarting.
<p><img src="images/api_tracing.png" alt="API Tools tracing"/></p>
</td>
</tr>
<tr id="ee-cleanup">
<td class="title">EE descriptions updated</td>
<td class="content">
The API Tools execution environment descriptions have been
updated with more accurate package information and have been renamed for easier installation.
To turn on warnings for invalid references to classes or methods that are not available in the configured execution environment, use the
<b>Plug-in Development > API Errors/Warnings</b> preference page.
<p>The execution environment descriptions can be installed from the Eclipse update site
(<a href="http://download.eclipse.org/eclipse/updates/4.2">http://download.eclipse.org/eclipse/updates/4.2</a>)
under the <b>API Tools Execution Environment Descriptions</b> category.</p>
<p><img src="images/eedesc.png" alt="Updated EE descriptions"/></p>
</td>
</tr>
<!-- ****************** END OF N&N TABLE ****************** -->
</table>
<p align="center"><a href="eclipse-news-part3.html">Previous</a> <font color="#808080">Next</font></p>
</body>
</html>
|
