Project Plan For Data Tools Platform, version 1.7
Introduction
"Data Tools" is a vast domain, yet there are a fairly small number of foundational requirements when developing with or managing data-centric systems. A developer is interested in an environment that is easy to configure, one in which the challenges of application development are due to the problem domain, not the complexity of the tools employed. Data management, whether by a developer working on an application, or an administrator maintaining or monitoring a production system, should also provide a consistent, highly usable environment that works well with associated technologies.
The Data Tools Platform (DTP) project provides a set of frameworks and basic tools to enable data-centric development in a variety of data types, including databases (via JDBC) and ODA data sources (for BIRT reporting). The frameworks are open to allow common interfaces (both API and user interface) across different types of data.
DTP is broken into a number of sub-projects, including the following:
- Connectivity: Provides basic frameworks for managing, connecting, and disconnecting from data sources
- Model Base: Provides EMF models for managing database and SQL details
- SQL Development Tools: Provides a set of frameworks and basic tools to handle management of database assets and SQL queries
- Enablement: Hosts contributions specializing DTP for specific data sources
- Incubator: Hosts new development in areas that are relevant to the other Eclipse Data Tools Platform projects, which because of their nature would not be appropriate for direct inclusion in the effected sub-project
Release Deliverables
Release Milestones
The DTP project delivers a set of components to ease connecting to and working with data sources. Primarily DTP focuses on database (SQL development) work and ODA data sources for BIRT reporting.
| M3 | 11/5/2008 | Release Train M3 +1 Date (M3 GA on 11/19/08) (Note that this will be the DTP 1.6.2 M1 build for now until we branch Galileo sometime the week of November 10th) |
| M4 | 12/17/2008 | Release Train M4 +1 Date (M4 GA on 1/12/09) |
| M5 | 2/3/2009 | Release Train M5 +1 Date (M5 GA on 2/16/09) |
| M6 | 3/16/2009 | Release Train M6 +1 Date (M6 GA on 3/23/09) |
| M7 | 5/4/2009 | Release Train M7 +1 Date (M7 GA on 5/11/09) |
| RC1 | 5/18/2009 | Release Train RC1 +1 Date (RC1 GA on 5/25/09) |
| RC2 | 5/25/2009 | Release Train RC2 +1 Date (RC2 GA on 6/1/09) |
| RC3 | 6/1/2009 | Release Train RC3 +1 Date (RC3 GA on 6/8/09) |
| RC4 | 6/8/2009 | Release Train RC4 +1 Date (RC4 GA on 6/15/09) |
| RC5 | 6/15/2009 | Release Train RC5 +1 Date (Galileo GA on 6/26/09) |
Target Environments
Though DTP has, up to its Ganymede release (1.6), been compiled against version 1.4 of the Java Platform APIs, starting with Galileo we will be compiling against version 1.5.0 of the Java Platform APIs. Our primary test environment will be with JDK 1.5 and we will test with JDK 1.6 as time and resources allow.
In addition, DTP will work on Eclipse Platform 3.5 and be backward compatible to Eclipse Platform 3.4.
Internationalization
DTP has been designed with localization in mind and will keep internationalization in mind as we go forward. As of DTP 1.6, we are also included in the Babel project.
Compatibility with Previous Releases
The goal of this release is to be backward compatible back to DTP 1.6.
Themes and Priorities
DTP in the Galileo timeframe will focus on the following themes:
(Note that "committed" items have the "plan" keyword in the BZ entry. "Proposed" items do not.)
Enhance DTP User Tooling
Enhance user tools to make DTP a compelling choice for developing data centric applications in Eclipse by providing additional exemplary tools in a variety of areas, including creation of database objects such as catalogs, schemas, tables, columns, constraints, and so on.
- Committed
- Enhance DTP User Tooling [247184] (target milestone: Galileo)
Improved DTP Support for RCP and Headless Applications
Enhance DTP to work better in headless and RCP applications.
- Committed
- Improve support for DTP in RCP applications [247744] (target milestone: Galileo)
Make DTP Easier for Extenders and Users
Make DTP easier to understand and leverage, from both the extender and user perspectives.
- Committed
- Make DTP Easier for Extenders and Users [252499] (target milestone: Galileo)
Continue Promoting and Expanding DTP Enablement support
DTP Enablement must continue on multiple fronts to promote and expand its support. This includes providing additional exemplary tools, encouraging community involvement, and promoting Incubator projects as they become ready. (Note there may be some duplication between the proposed items and the committed items.)
- Committed
- SQL server 2000/2005/2008 improvements [250302] (target milestone: Galileo)
- Proposed
- MySQL: catalogs and schemas inconsistent with other vendors [249013] (target milestone: Galileo)
- MySQL SQL formatter uppercase table names [105625] (target milestone: Galileo)
- For SQL Server, need connection option to filter system tables [252706] (target milestone: Galileo)
- unable to work offline with PostgreSQL [226704] (target milestone: Galileo)
- Sybase enablement plug-ins should be refactored for UI/non-UI separation [213390] (target milestone: Galileo)
Continued Enhancement of DTP Model Base
DTP Model base will continue enhancing the dbdefinition model and database vendor docs as well as respond to community requests for model changes.
Continued Enhancement of DTP SQL Dev Tools
DTP SQL Dev Tools will continue to focus on various SQL-related development tools, including the SQL Query Builder and SQL Editor frameworks, and additional tooling for creating and maintaining various SQL entities. Proposed items are for the SQL Query Builder, which we will implement as time and resources allow for Galileo.
- Committed
- UI code should be separated from editor.core plugin [252005] (target milestone: Galileo)
- Proposed
- Error logged when save and close a scrapbook to a sql file [241618] (target milestone: Galileo)
- Enhance DTP User Tooling [247184] (target milestone: Galileo)
- SQL Editor auto format [170602] (target milestone: Galileo)
- Overloading Function names [171718] (target milestone: Galileo)
- execute current statement [185501] (target milestone: Galileo)
- Editor does not inherit from STD text editors - specifically tabs [217923] (target milestone: Galileo)
- SQLToolsFacade doesn't recognise SQL server versions correctly [244180] (target milestone: Galileo)
- SQL Editor incorrectly specifies version number for open connections [244577] (target milestone: Galileo)
- SQL Statement Editor cannot save the content. [244682] (target milestone: Galileo)
- Scrollbar doesn't work in the grid mode [245484] (target milestone: Galileo)
- ResultExportWizard throws NPE when outputter.output throws Exception [246106] (target milestone: Galileo)
- SOE:Lost line focus after saving [246180] (target milestone: Galileo)
- Remember result tab while iterating through results [254488] (target milestone: Galileo)
- Multi-page SQL Schema Editor Framework & exemplary implementations for Sybase ASA in enablement project [256368] (target milestone: Galileo)
- poor error handling in datatools when browser can't be started [221362] (target milestone: Galileo)
- Show the elapsed run time of a SQL [231401] (target milestone: Galileo)
- Add ability to select individual cells in the Results View and copy to clipboard [243778] (target milestone: Galileo)
- sql editor opens by default [220318] (target milestone: Galileo)
- postgresql code assist didn't work in SQL File Editor [237037] (target milestone: Galileo)
- Support for auto-commit and commit/rollback buttons [243779] (target milestone: Galileo)
- UI code should be separated from editor.core plugin [252005] (target milestone: Galileo)
- Inconsistent behavior on execution [221845] (target milestone: Galileo)
- RoutineEditor to open different SQL Objects with same name [199353] (target milestone: Galileo)
Individual DTP Sub-Project Plans
Project Plans:
