Re: [wtp-proposal] changes of the new Eclipse Web Tools proposal

["Xinjie ZHANG" <xjzhang78@xxxxxxxxxxx>]

Does anyone know whether the Eclipse Board has approved this project or not?
Why there are no further news after May 27 ? Have the date and place of the
kick-off meeting been finally fixed?

----- Original Message ----- 
From: "Dominique DE VITO" <dominique.devito@xxxxxxxxxxxxx>
To: <wtp-proposal@xxxxxxxxxxx>
Sent: Thursday, May 27, 2004 8:19 PM
Subject: [wtp-proposal] changes of the new Eclipse Web Tools proposal


>
> The new Eclipse Web Tools proposal has been published on www.eclipse.org.
>
> Main changes are related to :
> - a more precise and a clearer expression of what's in and out of the
scope of
> each subproject.
> - add of new contributors: Gorkem Ercan, Jens Lukowski and Xinjie Zhang!
and
> corresponding contributions details.
>
> I have collected the changes summarized and detailled below.
>
> Regards,
> Dominique De Vito
> Thales+ObjectWeb
>
>
> ========================================
>
> Change list summary:
> - improvment of what's in and out of the scope of each subproject.
> - add of new contributors: Gorkem Ercan, Jens Lukowski and Xinjie Zhang!
and
> corresponding contributions details.
> - add of Erich Gamma to the Candidate PMC members list.
> - better 'Becoming a committer' documentation
> - a new J2EE architectural principle and a new use case
> - other changes: rephrasing, typos...
>
> ========================================
>
> Change list details:
>
> * page 'main':
>
> - Rephrasing (as a person was thinking that Eclipse was planning a new OSS
J2EE
> server implementation) :
>
> Within scope will be a workbench providing a framework for developing,
deploying,
> testing and debugging J2EE applications on standards-compliant server
> environments, as well as an exemplary implementation for an open source
J2EE
> Server
>
> =>
>
> Within scope will be a workbench providing a framework for developing,
deploying,
> testing and debugging J2EE applications on standards-compliant server
> environments, as well as an exemplary implementation of a plug-in for at
least an
> open source J2EE Server.
>
> ========================================
>
> * page 'Web Standard Tools':
>
> - add of SVG support more explicitly
>
> - refactored project context:
>
> Support of Web standards in the scope of the Web Standard Tools subproject
> includes languages and specifications published by open-standard bodies
(e.g. W3C,
> IETF, ECMA, OASIS, WS-I, ANSI) that are commonly used by Web-centric
applications
> (e.g. HTML, CSS, JavaScript, XML, XSD, XSLT, SVG, SOAP, WSDL, UDDI, SQL,
XQuery).
>
> This subproject will provide support for integrating Web servers into
Eclipse as
> first-class execution environments for Web applications. This support will
include
> the ability to configure Web servers and assocaite them with Web projects.
> Examplar tools for supporting popular Open Source Web servers, such as
Apache, are
> in scope.
>
> Support of JCP standards are explicitly outside the scope of this project
and
> should be covered by the Java Development Tools (JDT) project or by the
J2EE
> Standard Tools (JST) subproject.
>
> The subproject will provide tools that directly support the base standards
and
> that are also extensible. For example, the HTML editor will be extensible
to
> support HTML-based template languages such as PHP and JSP. While a JSP
editor is
> in the scope of the JST subproject, exemplar tools for popular Open Source
> languages such as PHP are in scope.
>
> The goal of this project is to provide both
>
> ========================================
>
> * page 'J2EE Standard Tools':
>
> - refactored project context:
>
> The scope of the J2EE Standard Tools subproject is the support of J2EE
> programming. This includes the support of APIs covered by the J2EE1.4
> specifications (e.g. JSP, Servlets, EJBs, JCA, JMS, JNDI, JDBC, Java Web
Services,
> JAX* and related JSRs). Support for JCP specifications commonly used in
Web
> Applications, but not included in J2EE1.4 is to be studied on a case by
case basis
> (ex: JSF,JDO).
>
> Support of frameworks not covered by the JCP (ex: Struts, Hibernate, XMLC)
is
> outside the scope of this project, such projects could find a home in the
Eclipse
> Technology project.
>
> JST will have annotation support (JSR 175-Metadata), on top of those
provided in
> the JDT, e.g. for code assist, where applicable. Annotation support will
include
> JSR 181-Metadata for Web Services, and in the future will include support
for
> other standardized metadata such as EJBs. In the transitional period until
there
> are JSRs for J2EE annotations, JST will have some support for widely
accepted open
> technologies such as XDoclet.
>
> - new architectural principle:
>
> Provide modular design of tools for enabling separate tool deliveries for
> differents classes of developers
>
>   Enable separate deliveries of servlet/JSP and EJB tools
>
>   Etc
>
> - add of "support for JSR-109 Implementing Enterprise Web Services":
>
> Java Web Services and support for JSR-109 Implementing Enterprise Web
Services
>
> - new use case:
>
> Provide Exemplar Server Tools for open-technology server runtimes such as
Apache
> Tomcat, JOnAS, JBoss, J2EE 1.4 SDK and others.
>
> ========================================
>
> * page 'Contributing To The WTP Project':
>
> - change of the 'Communicating Your Desires/Intentions' paragraph to add
the
> sentences:
>
> The mailing lists and/or newgroups could also be used for discussing or
proposing,
> in a more informal way, enhancements or new capabilities. Anyway Buzilla
is seen
> here as a central repository of reference for enhancement demands
>
> - extraction of paragraphs' sentences to create a 'Becoming a committer'
> paragraph:
>
> Becoming a committer
>
> Every developer's contribution is welcomed. And by the time, developers
can become
> committers. A committer is a developer who has write access to the source
code
> repository for the associated subproject (or component), and has voting
rights
> allowing to affect the future of the subproject (or component); other
developers
> define patches and submit them, indirectly, through committers. A
developper gains
> such committer rights through frequent and valuable contributions to a
subproject,
> or component of a subproject (in the case of large subprojects). For more
> information in what it means to be or to become an Eclipse project or
subproject
> committer, see the WTP Project Charter. We should point out that creating
and
> submitting quality patches is the best way to obtain committer privileges
for
> future work.
>
> - add the (missing) reference to 'CDT Documentation Style Guide'
>
> ========================================
>
> * page 'Project Development Plan'.
>
> - add of new contributors: Gorkem Ercan, Jens Lukowski and Xinjie Zhang!
and of
> their contributions details!
>
> - correction of name typos
>
> ========================================
>
> * page 'Project Management Committee':
>
> - Erich Gamma has been added to the Candidate PMC Members list
>
> ========================================
>
> * page 'FAQ':
>
> -  Changes about the possible meeting:
>
> Upon formal Eclipse approval of the project. A four-day
introduction/presentation
> of contributions/vision/architecture brainstorming session will start the
project.
> INRIA has offered to host the event in Grenoble, France from June 16th to
June
> 19th.
>
> ========================================
>
> * page 'Designer Documentation' : no change
>
> * page 'Monthly Conference Calls': syntax change.
>
> * page 'IBM contribution' : no change
>
> * page 'ObjectWeb and Eteration' contribution : syntax change.
>
> * page 'Reference Documentation' : no change
>
> * page 'Project Structure' : no change
>
> * page 'Project Charter' : no change
>
> * page 'User Documentation' : no change
>
> * page 'Downloads' : no change
>
> * page 'Unit Test Guidelines' : no change
>
>
>
>
> _______________________________________________
> wtp-proposal mailing list
> wtp-proposal@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/wtp-proposal
>