Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse4/KnownIssues/4.1"
(New page: The Eclipse 4.1 SDK is already substantially ready. We on the Platform team have been using it for months and are generally satisfied with its usability, performance and robustness, and th...) |
|||
| Line 1: | Line 1: | ||
The Eclipse 4.1 SDK is already substantially ready. We on the Platform team have been using it for months and are generally satisfied with its usability, performance and robustness, and the overall rate of convergence. By the time 4.1 ships, we expect that the Eclipse community at large should be able to use it for development without impacting their productivity and would even expect that most plug-ins will run correctly on top of it. | The Eclipse 4.1 SDK is already substantially ready. We on the Platform team have been using it for months and are generally satisfied with its usability, performance and robustness, and the overall rate of convergence. By the time 4.1 ships, we expect that the Eclipse community at large should be able to use it for development without impacting their productivity and would even expect that most plug-ins will run correctly on top of it. | ||
| − | The focus on 4.1 has been: | + | The focus on 4.1 has been on bringing it up to a point where it's functionally usable on a day-to-day basis. we've achieved this at least to the point where we feel confident enough to garner input from a wider audience in the eclipse community. There are however parts of the existing eclipse |
| + | |||
| + | : | ||
| + | |||
API Completeness: Ensuring that we have the ability to seamlessly run at least the majority of plug-ins. | API Completeness: Ensuring that we have the ability to seamlessly run at least the majority of plug-ins. | ||
Robustness: Making sure that you can work with 4.1 in the same manner that you do currently with the 3.x stream. | Robustness: Making sure that you can work with 4.1 in the same manner that you do currently with the 3.x stream. | ||
Revision as of 17:16, 9 March 2011
The Eclipse 4.1 SDK is already substantially ready. We on the Platform team have been using it for months and are generally satisfied with its usability, performance and robustness, and the overall rate of convergence. By the time 4.1 ships, we expect that the Eclipse community at large should be able to use it for development without impacting their productivity and would even expect that most plug-ins will run correctly on top of it.
The focus on 4.1 has been on bringing it up to a point where it's functionally usable on a day-to-day basis. we've achieved this at least to the point where we feel confident enough to garner input from a wider audience in the eclipse community. There are however parts of the existing eclipse
API Completeness: Ensuring that we have the ability to seamlessly run at least the majority of plug-ins. Robustness: Making sure that you can work with 4.1 in the same manner that you do currently with the 3.x stream.
There are a number of known issues that you will immediately notice when using Eclipse 4.1:
No Intro: While serious for enterprise products this will generally not affect the functionality of the system
Menu/TB Issues:
We are still experiencing ordering issues with menu and toolbar items. There may be instances where an item is visible or enabled when it should not be.