Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] M4 API Status


All proposed APIs that have a shortfall in Javadoc or JUnit coverage will be deferred to a future release and will be renamed to "internal.provisional", with the exception of the J2EE Model.

J2EE Model


The J2EE Model provides an API for the set of J2EE deployment descriptors, e.g. web.xml, application.xml. The J2EE Model API currently has a large JUnit shortfall (1200 methods are untested). However, this API is automatically generated from EMF models. We feel the model is well designed and mature, the Javadoc coverage is good, and the code has been used in products. We therefore propose to give this component a pass for M4 on the condition that the JUnit coverage be dramatically improved.

Our strategy for improving the JUnit coverage is to generate the test cases from a bucket of example deployment descriptors. Jeffrey Liu is currently prototyping this approach. We are also planning to review the situation with the EMF team to get their guidance.

Data Tools


All non-API code currently obeys the naming convention that requires the inclusion of the keywork "internal" in the package name, with the exception of the Data Tools. The Data Tools are planned to move to the DTP project, and will therefore not be API in WTP. However, we have been informed that another development project is using the currently version for an upcoming beta release, and they have requested that we defer the rename. Since it is important for the success of WTP to prmote a thriving ecosystem of adopters, we should be sensitive to this type of request. I therefore support this request and recommend that the PMC grant the Data Tools this exception for M4. I will work with the Data Tools team to establish a mutually acceptable date for the rename.

WTP 1.0.1

I have received a request from a planned product  that WTP provide a point release towards the end of the year to include fixes, and to declare key defered APIs. I have requested a complete list of the APIs they require. This point release would coincide with an Eclipse platform point release. I recommend we plan for this point release to satisfy this, and potentially other, product requirements.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx
intranet: http://labweb.torolab.ibm.com/DRY6/


Back to the top