Difference between revisions of "Web Tools Platform 2.0 Plan"

From Eclipsepedia

Jump to: navigation, search
(Compatibility with Other WTP Releases)
(Release milestones and release candidates)
Line 47: Line 47:
 
==Release milestones and release candidates ==
 
==Release milestones and release candidates ==
  
Release milestone occurring at roughly 6 week intervals in synchronisation with the Eclipse Platform milestone releases (starting with M1) and will be compatible with Eclipse 3.3 builds. See [http://www.eclipse.org/projects/callisto.php Callisto Simultaneous Release] for the Eclipse Platform schedule from 2006 on which the 2007 calendar will be based. (Note that this is not yet available, and that the dates below are simply a placeholder carried over from last year.)
+
Release milestone occurring at roughly 6 week intervals in synchronisation with the Eclipse Platform milestone releases (starting with M1) and will be compatible with Eclipse 3.3 builds. See [http://www.eclipse.org/projects/callisto.php Callisto Simultaneous Release] for the Eclipse Platform schedule from 2007 on which the 2008 calendar will be based. (Note that this is not yet available, and that the dates below are simply a placeholder carried over from last year.)
  
 
The milestones and release candidates are:  
 
The milestones and release candidates are:  
  
  * M4  -    January 13, 2006
+
  * M4  -    January 13, 2007
  * M5  -    March 3, 2006 (planned API freeeze)
+
  * M5  -    March 3, 2007 (planned API freeeze)
  * M6/RC0  -    April 14, 2006 (This is Feature Freeze except for JSF and Dali).  
+
  * M6/RC0  -    April 14, 2007 (This is Feature Freeze except for JSF and Dali).  
 
                             (this 4/14 date is also called both RC0 and RC1 in Callisto plan).
 
                             (this 4/14 date is also called both RC0 and RC1 in Callisto plan).
  * RC1 -    April 21, 2006
+
  * RC1 -    April 21, 2007
  * RC2 -    May 5, 2006 (tiny grace period where any safe fix can be made).  
+
  * RC2 -    May 5, 2007 (tiny grace period where any safe fix can be made).  
  * RC3 -    May 19, 2006 (component lead approval required for all fixes)
+
  * RC3 -    May 19, 2007 (component lead approval required for all fixes)
  * RC4 -    May 31, 2006 (planned code freeze, PMC approval required for all fixes)
+
  * RC4 -    May 31, 2007 (planned code freeze, PMC approval required for all fixes)
  * RC5 -    June 20, 2006 (PMC approval and adopter sign-off required for all fixes)
+
  * RC5 -    June 20, 2007 (PMC approval and adopter sign-off required for all fixes)
  * RC6 -    Jume 28, 2006 Golden Master
+
  * RC6 -    Jume 28, 2007 Golden Master
  * Release - June 30, 2006 - WTP 1.5 Release (part of the "Callisto" joint release)
+
  * Release - June 30, 2007 - WTP 1.5 Release (part of the "Callisto" joint release)
  
 
==Target Operating Environments==
 
==Target Operating Environments==

Revision as of 17:04, 11 May 2006

Contents

Eclipse Web Tools Project DRAFT 2.0 Plan

Revised draft April 25, 2006 (by Tim Wagner / based on WTP Project 1.5 Plan and Eclipse Project DRAFT 3.3 Plan)

Please send comments about this draft plan to the wtp-pmc@eclipse.org mailing list.

This document lays out the feature and API set for the next feature release of Eclipse Web Tools after 1.5, designated release 2.0. This document is a draft and is subject to change, we welcome all feedback.

Web Tools 2.0 will be compatible with / based on the Eclipse 3.3 Release.

To ensure the planning process is transparent and open to the entire Eclipse community, we (the Eclipse Web Tools Requirement Group & the Web Tools PMC) post plans in an embryonic form and revise them throughout the release cycle.

The first part of the plan deals with the important matters of release deliverables, release milestones, target operating environments, and release-to-release compatibility. These are all things that need to be clear for any release, even if no features were to change.

The remainder of the plan consists of plan items for the subprojects under the Eclipse Web Tools top-level project, including projects such as JSF and Dali that are currently in the incubator state. Each plan item covers a feature or API that is to be added to Web Tools, or some aspect of Web Tools that is to be improved. Each plan item will have its own entry in the Eclipse bugzilla database, with a title and a concise summary (usually a single paragraph) that explains the work item at a suitably high enough level so that everyone can readily understand what the work item is without having to understand the nitty-gritty detail.

With the previous release as the starting point, this is the plan for how we will enhance and improve it. Fixing bugs, improving test coverage, documentation, examples, performance tuning, usability, etc. are considered routine ongoing maintenance activities and are not included in this plan unless they would also involve a significant change to the API or feature set, or involve a significant amount of work. The intent of the plan is to account for all interesting feature work.


The current status of each plan item is noted:

High Priority plan item - A high priority plan item is one that we have decided to address for the release (committed).

Medium Priority plan item - A medium priority plan item is one that we are considering addressing for the release. Although we are actively investigating it, we are not yet in a position to commit to it, or to say that we won't be able to address it.

Low Priority plan item – A low priority plan item is one that we addressed for a release we will only address that item if one component has addressed all high and medium priority items

Deferred plan item - A reasonable proposal that will not make it in to this release for some reason is marked as deferred with a brief note as to why it was deferred. Deferred plan items may resurface as committed plan items at a later point.


Release deliverables

The release deliverables have the same form as previous releases, namely:

  • Source code release for Eclipse WTP Project, available as versions tagged "R2_0" in the Eclipse WTP Project
  • CVS repository
  • Eclipse WTP runtime binary and SDK download with all Eclipse pre-reqs (downloadable).
  • Eclipse WTP runtime binary and SDK download (downloadable).

In addition, the Eclipse WTP runtime binary and SDK will be available as part of the "Callisto '07" update site.

Release milestones and release candidates

Release milestone occurring at roughly 6 week intervals in synchronisation with the Eclipse Platform milestone releases (starting with M1) and will be compatible with Eclipse 3.3 builds. See Callisto Simultaneous Release for the Eclipse Platform schedule from 2007 on which the 2008 calendar will be based. (Note that this is not yet available, and that the dates below are simply a placeholder carried over from last year.)

The milestones and release candidates are:

* M4  -     January 13, 2007
* M5  -     March 3, 2007 (planned API freeeze)
* M6/RC0  -     April 14, 2007 (This is Feature Freeze except for JSF and Dali). 
                           (this 4/14 date is also called both RC0 and RC1 in Callisto plan).
* RC1 -     April 21, 2007
* RC2 -     May 5, 2007 (tiny grace period where any safe fix can be made). 
* RC3 -     May 19, 2007 (component lead approval required for all fixes)
* RC4 -     May 31, 2007 (planned code freeze, PMC approval required for all fixes)
* RC5 -     June 20, 2007 (PMC approval and adopter sign-off required for all fixes)
* RC6 -     Jume 28, 2007 Golden Master
* Release - June 30, 2007 - WTP 1.5 Release (part of the "Callisto" joint release)

Target Operating Environments

Eclipse WTP is built on the Eclipse platform itself.

Most of the Eclipse WTP is "pure" Java™ code and has no direct dependence on the underlying operating system. The chief dependence is therefore on Eclipse. The 2.0 release of the Eclipse WTP Project is written and compiled against version 5 of the Java Platform APIs, and targeted to run on version 5 (aka 1.5) of the Java Runtime Environment, Standard Edition.

Eclipse WTP is mainly tested and validated on Windows platforms, it should run on all platforms validated by the platform project (note that this link below is outdated but a new version is not yet available):

Eclipse Target Operating Environments

Servers integrated into Eclipse WTP deliverables will be tested and validated on the same platforms listed above. Tests for other platforms will be relying on the community support.


Internationalization

The Eclipse WTP is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. Other language support, if any, will rely on the community support.

Compatibility with Other WTP Releases

Project Compatibility:

  • Binary compatibility with 1.5 and 1.0 projects - users should need to take no special actions to use projects
 from either of these WTP releases with the 2.0 version
  • WTP 2.0 should be able to open workspaces created with WTP 1.5
  • WTP 2.0 should be usable in a team environment where some team members use WTP 1.5 and team members share projects through a source code control system such a CVS or Subversions. Specifically, A WTP 1.5 should be able to create a project, check it in to the repository. A WTP 2.0 user should be able to check it out, work on it, and check it back in. A WTP 1.5 should then be able to check it back out and continue to work it on.
  • A WTP 1.5 should also be able to work on projects created by WTP 2.0 users and shared via a repository. Any new artifacts creates by WTP 2.0 should not break WTP 1.5. WTP 1.5 should either ignore or tolerate any new artifacts created by WTP 2.0.

API Compatibility:

  • WTP 2.0 will preserve (public, declared) API compatibility with the 1.5 release, both in terms of syntax and behaviour
  • A plug-in that is developed on WTP 1.5 and that uses no internal methods should run correctly without recompilation on WTP 2.0
  • A plug-in that is developed on WTP 1.5 and that uses no internal methods should recompile without error on WTP 2.0
  • WTP 2.0 should provide migration notes and adequate notification and lead time to adopters for any internal code that is removed in WTP 2.0
  • WTP 2.0 should continue to provide adopters with the ability to register their code usage reports and to be consulted in any proposed changes to internal code. WTP 2.0 will take into account adopter feedback on proposed changes to internal code, but reserves the right to change internal notwithstanding that feedback.

Eclipse WTP 2.0 deliverables will be compatible with Eclipse 3.3. No special attention will give for being compatible with previous Eclipse versions.

Eclipse WTP Subprojects

The Eclipse WTP consists of four subprojects. Each subproject is covered in its own section:

Web Standard Tools (WST)

J2EE Standard Tools (JST)

Java Server Faces Tools (JSF, incubating)

JPA (Dali/JPA, incubating)

AJAX Tools Framwork (incubating)

The JSF, Dali, and ATF incubators SHOULD exit incubation and become normal components in WTP 2.0. A partial list of the new WTP components is:

  • JSF - org.eclipse.jst.jsf
  • Dali - org.eclipse.jst.jpa
  • ATF - org.eclipse.wst.js, org.eclipse.wst.ajax

Items listed reflect new features of the Web Tools Platform, or areas where existing features will be significantly reworked. Common goals are listed in the “Common goals” area.

TBD (Each item indicates the components likely affected by that work item (many items involve coordinated changes to several components). Numbers in parentheses link to bugzilla problem reports for that plan item)

Note that JSF and JPA/Dali are incubating projects at the moment. Users should expect API and tool refinements in these areas, with a likelihood for more rapid (and extensive) revisions than in the base WTP code, along with initial API declarations in the 2.0 release.

Common goals

Adopter readiness

Improved Provisioning of Third Party Content

  • create remote Update Manager sites hosted by providers of third party content required by WTP to streamline the process of adopting new versions
  • users should be able to acquire revisions of third party content in a more timely fashion
  • begin by creating a common site at Apache for components such as Axis2, Woden, Tomcat, Geronimo
  • maintain and expand current site at SourceForge as required
  • create new site at ObjectWeb for Jonas

Help

  • adopt DITA for Help content
  • work with DITA-OT project at SourceForge to improve integration of build process with PDE

Web Standard Tools subproject

XML Editing

  • Code folding
  • Improved formatting, e.g. whitespace handling, WYSIWYG (for DITA, DocBook, etc.)
  • Run in Eclipse RCP
  • Large document performance enhancements

Architectural harmonization

DTP

Adopt DTP. Remove all Data access tools from WTP and instead use the corresponding components from DTP. We should take a two-phase approach.

  • Phase 1 - Acheive functional parity with WTP 1.5, i.e. get back to where we currently are, but using DTP.
  • Phase 2 - Exploit new DTP capabilites. DTP has much broader scope than the WTP 1.5 Data tools, e.g. in connection management, server exploration. We need to do an architectural assessment of current WTP capabilities and adopt superior alternatives available in DTP.

STP

Investigate areas of overlap with STP, especially in the areas of Web services, and ensure that existing WTP components can be extended as required by STP.

TPTP

Improve integration with TPTP, especially in the area of profiling servers.

PHP Tools Project

Investigate if the Apache Web server adapter should be moved into wst.server. Investigate if other generic components currently in the PHP project should be moved in WTP.

Web Services Support

  • New WS-I Profiles, e.g. RAMP
  • WS Security
  • WS Policy
  • Axis 2.0
  • SOAP 1.2
  • WSDL 2.0 - adopt Apache Woden 1.0

WSDL 2.0

WSDL is a key Web service artifact. WSDL 2.0 is the W3C standard and has many new features that align Web services with Web architecture, especially in the area of HTTP support and REST style Web services. All WTP tools that currently process WSDL 1.1 should be upgraded to handle WSDL 2.0. The integration should be seamless in the sense that the tools should understand both WSDL 1.1 and WSDL 2.0. All wsdl files will use the same file extension, i.e. *.wsdl. These tools include:

  1. WSDL editor - editor should detect namespace
  2. WSDL validator - validator should detect namespace
  3. Web service explorer
  4. Web service test tools - the WS-I test tools should be extended to support services described by WSDL 2.0 based on the W3C standard, e.g. verify the message log conforms to a WSDL 2.0 description
  5. Web service wizard - e.g. via integration with Axis 2.0 to support top-down, bottom-up, and client code generation based on WSDL 2.0

J2EE Standard Tools

Java EE 5

  • JPA/Dali
  • JSF
    • JSF 1.2
    • JSP 2.1
  • Java EE 5 models - the models must be upgraded to handle Java EE 5 without ANY API breakage. Existing clients MUST continue to work without recompilation. If existing clients are recompiled with the new model, then compilation errors MUST NOT occur (note: we assume that existing clients will not break in any way if they only use the published API - code that relies on internal interfaces MAY break)
  • JSR 175 - support Java EE 5 specifications for annotation based programming, e.g. for EJB 3.0, JPA, Web services
    • JSR 181 - Web Services
    • JSR 220 - EJB 3.0, JPA

Web Services

  • JSR 109 - for Web container
  • support for generic, compliant runtime, e.g. hosted at GlassFish

Server Runtime

  • JSR 88 Support, Advanced Server Support for one/multiple open source J2EE server
  • Server runtime facet enhancements (link TBD)
  • Migrate existing bundled server adapters to the remote server adapter support - our direction should be to have server providers host their own adapters as they currently do for their runtimes. Server providers should also be encourage to use the remote server runtime installation framework (currently used by Geronimo)