| 118 |
<li>Implement an Equinox OSGi Framework launcher</li> |
<li>Implement an Equinox OSGi Framework launcher</li> |
| 119 |
<li>Add a "3.2" target version in the New Plug-in Project creation wizard |
<li>Add a "3.2" target version in the New Plug-in Project creation wizard |
| 120 |
and start generating manifest files for the 3.2 runtime.</li> |
and start generating manifest files for the 3.2 runtime.</li> |
|
<li>Automated management of exported packages in a plug-in. Come up |
|
|
with a tooling equivalent of the old <export name="*"/></li> |
|
| 121 |
<li>More refactoring: renaming a package in an Export-Package header should |
<li>More refactoring: renaming a package in an Export-Package header should |
| 122 |
result in the renaming of that package in all client bundles that have |
result in the renaming of that package in all client bundles that have |
| 123 |
imported it.</li> |
imported it.</li> |
| 136 |
<li>Implement an NLS wizard to externalize plug-in manifest files</li> |
<li>Implement an NLS wizard to externalize plug-in manifest files</li> |
| 137 |
</ul> |
</ul> |
| 138 |
</li> |
</li> |
| 139 |
<li>Quick fixes (Investigation)<ul> |
<li>Quick fixes<ul> |
| 140 |
<li>Investigate a quick fix support on manifest files.</li> |
<li>Add quick fix support to manifest.mf files.</li> |
| 141 |
<li>The pioneer quick fix would be the one to fix the soon-to-be-deprecated |
<li>The pioneer quick fix would be the one to fix the soon-to-be-deprecated |
| 142 |
Eclipse-AutoStart header.</li> |
Eclipse-AutoStart header.</li> |
| 143 |
|
<li>Add quick fixes to resolved dependency problems.</li> |
| 144 |
</ul> |
</ul> |
| 145 |
</li> |
</li> |
| 146 |
<li>New Source Lookup (investigation)<ul> |
<li>Manifest management<ul> |
| 147 |
<li>start the investigation</li> |
<li>Add a context menu item that organizes the Import-Package, Require-Bundle |
| 148 |
<li>co-ordinate with the Debug and Core teams on what pieces need to be in |
and Export-Package headers of a manifest.mf file</li> |
| 149 |
place.</li> |
</ul> |
| 150 |
|
</li> |
| 151 |
|
<li>Search<ul> |
| 152 |
|
<li>Participate in Java searches to reveal search hits in manifest files.</li> |
| 153 |
|
</ul> |
| 154 |
|
</li> |
| 155 |
|
<li>Enhance dependency validation<ul> |
| 156 |
|
<li>Leverage the new state APIs to determine more precisely the unsatisfied |
| 157 |
|
constraints of unresolved bundles.</li> |
| 158 |
|
<li>add support to the PDE launchers to optionally perform the validation |
| 159 |
|
prior to every launch.</li> |
| 160 |
</ul> |
</ul> |
| 161 |
</li> |
</li> |
| 162 |
<li>Reduce the defect backlog.</li> |
<li>Reduce the defect backlog.</li> |
| 163 |
</ul> |
</ul> |
| 164 |
|
<p> </p> |
| 165 |
|
<p> <b><font size="3">3.2 Development Effort - Milestone </font></b> |
| 166 |
|
<font size="3"><b>4 (December 16, 2005)</b></font></p> |
| 167 |
|
<ul> |
| 168 |
|
<li>Editors<ul> |
| 169 |
|
<li>Add syntax highlighting to the manifest.mf source page.</li> |
| 170 |
|
</ul> |
| 171 |
|
<ul> |
| 172 |
|
<li>In the product editor, add the option to specify different program/VM arguments per platform (linux, |
| 173 |
|
macosx, solaris, win32).</li> |
| 174 |
|
<li>Start leveraging the upcoming Eclipse Forms error reporting in PDE |
| 175 |
|
editors.</li> |
| 176 |
|
</ul> |
| 177 |
|
</li> |
| 178 |
|
<li>Schema Editor<ul> |
| 179 |
|
<li>Rework the entire editor for improved usability.</li> |
| 180 |
|
<li>Add support to deprecate extensions and specify a replacement.</li> |
| 181 |
|
<li>Add support to specify whether a client of an extension must add the |
| 182 |
|
plug-in to its list of dependencies.</li> |
| 183 |
|
</ul> |
| 184 |
|
</li> |
| 185 |
|
<li>Execution Environment<ul> |
| 186 |
|
<li>Connect the runtime's notion of an execution environment with the new |
| 187 |
|
upcoming concept in JDT/Debug</li> |
| 188 |
|
<li>Tie the entire Execution Environment together.</li> |
| 189 |
|
</ul> |
| 190 |
|
</li> |
| 191 |
|
<li>Target Management<ul> |
| 192 |
|
<li>Relax the rules when resolving the target platform to exclude only |
| 193 |
|
unresolved singleton plug-ins</li> |
| 194 |
|
<li>Introduce an org.eclipse.pde.core.targetProfiles extension point for |
| 195 |
|
people to contribute target profiles</li> |
| 196 |
|
<li>Contribute two feature-based target profiles (RCP and SDK)</li> |
| 197 |
|
<li>Implement a Target Profile editor</li> |
| 198 |
|
<li>Introduce easy ways to switch target profiles: via a context menu and on |
| 199 |
|
the target platform preference page.</li> |
| 200 |
|
</ul> |
| 201 |
|
</li> |
| 202 |
|
<li>Automated management of manifest.mf files<ul> |
| 203 |
|
<li>Allow users to augment their plug-in development classpath by adding |
| 204 |
|
potential dependencies to the build.properties file.</li> |
| 205 |
|
<li>As users use code from these potential dependencies, manage the |
| 206 |
|
manifest.mf by modifying the Import-Package/Require-Bundle appropriately.</li> |
| 207 |
|
</ul> |
| 208 |
|
</li> |
| 209 |
|
<li>Reduce the defect backlog</li> |
| 210 |
|
</ul> |
| 211 |
<p> </td> |
<p> </td> |
| 212 |
</tr> |
</tr> |
| 213 |
<tr> |
<tr> |