Skip to main content
Jump to: navigation, search

WTP 2008-04-10

WTP Development Status Meeting 2008-04-03


Project Leads
Nitin Y
Kathy Y
Chuck Y
Neil Y
David Y
Helen Y
Dave Y
Phil Y
Kaloyan Y
Amy Y
Kate Y
Angel Y
Nick Y
Gilbert Y

Announcements And Reports

  • WTP temp update site for testing
  • Minutes:

Ganymede site should be available in the next couple of days

Focus on Requirements Planning (Raghu)

Projects with no committed items: none
Please update status page
  • Please review untriaged enhancement requests
Untriaged Enhancement Requests ()
  • Reminder: Any feature work that slips past M6 needs PMC review, and needs to be explicitly listed on ramp down page. (Before the end of M6!)
David will update docs and send reminder note.
Document updated to clarify policy. See WTP 3.0 Ramp down Plan for Ganymede
  • Minutes:
Raghu: For the Requirement section, apart from JEE and Server Tolls, the doc is looking good. There are still items that are committed, but not completed, though we are technically in a Feature freeze. It is the only item worth calling out in the meeting.
Angel and Chuck will review doc for server and JEE

Post WTP 2.0.2

  • Done for now, but .... some issues are still being investigated.
  • Minutes
David: may have future patches, with reopened and new bugs, currently being investigated

WTP 3.0 M7

  • our +2 date: Tuesday, May 6 2008
  • Final Code released by April 25th
Plan 04/07 - 04/11
Development 04/14 - 04/25
Test 04/28 - 05/02
RC1 05/20
RC2 05/27
User/SDK docs can be updated up to M7 (maybe RC1? -- I'll ask Helen to advise us)

  • Bug Lists
3.0 Invalid Targeted Bugs (~13)
3.0 M7 Targeted Bugzilla Enhancements (~10)
All Remaining 3.0 Targeted Enhancements (~98)
3.0 M7 Remaining Targeted Bugs (~148)
3.0 M7 Hot Bug Requests (~0)
3.0 M7 Hot Bugs (~1)
3.0 M7 Blockers/Criticals (~0)
3.0 M7 JST, WST, JSF Bugs Fixed (~30)
3.0 M7 JPT Dali Bugs Fixed (~20)
3.0 Untargeted Blockers/Criticals (~2)
3.0 Resolved, Unverified Blockers/Criticals (~30) By Assignee
  • Minutes:
[hotbug]: Larry/Chuck, will review and check release into build asap
untargeted critical/blockers: Angel: will review with Tim, and put up for PMC review if needed
M6 reminders to close verified bugs, and to move off M6 bugs
Gary: Convention for closing bugs that's not been verified for 1 month?
Kathy: usually send a reminder to originator then verify and close
David: should be verified before milestone, and definitely before release is done

Performance Focus (Kaloyan)

Some (possible) progress on debugging the problem with running the tests. Seems related to org.eclipse.test.performance

We'll begin having weekly performance section to review tests and test results.

Update 2008-03-06: We have identified that changes made in bug 201469 could be a potential reason for the Derby error:

ERROR 42Y07: Schema 'GUEST' does not exist

The changes in the bug are about improving performance, but they also affect the org.eclipse.test.internal.performance.db.DB class and if we compare between revisions 1.68 and 1.70 we could see that the changes deal with some user and password settings. Now it is not clear what should be changed in the WTP perf tests setup to comply with this change. May be setting some user and password for Derby?!

Update 2008-03-13: We have found an interesting article about Derby that seems to explain the problem. There it is explained that if the database is accessed without authentication, then the default database schema is APP. This is our case before the changes of bug 201469. But, if authentication is used, then the default schema becomes the username. After the changes of bug 201469 all access to the DB is done through the default user Guest. The DB driver tries to find the tables in schema GUEST instead of in schema APP. This explains the Error message above.

We see the best solution is to rename the schema in our Derby database from APP to GUEST for builds after bug 201469. We are now investigating how to do this.

  • Minutes:
David: Generate db with platform test plugin, then things are okay, asked for the earlier build to be restored in the update site. Making progress on this, hopefully will have more report in 2 weeks

Update 2008-03-27: DB issue resolved. Just setting DB user and DB password to "app" on newer builds solves the problem. We have now perf results for M3 and M4.

It seems that we have new problems with M5. It takes much longer (~33 hours compared to ~11 hours) and the wtpperflog is huge (120 MB) and full with dumps and errors. I need some time for further investigation of the problem.

Update 2008-04-10: The reason for the plugin start failure was that the xsd-runtime binary was not extracted by the procedure. This is now fixed. Other issues are faced. In M5 we have OutOfMemoryError, heap memory is now increased and tests are running again. In M6 we have StackOverflowError - probably a bug in the Platform.

API Tools/Scans (Kaloyan)

Current ones will be ending soon. Kaloyan volunteered to explore the new Platform API tools, to make recommendations to WTP or build process.

Update 2008-03-06: I have started exploring and evaluating the Api Tooling project. It is planned to become part of Eclipse 3.4 by the end of M6. Now it is available only by checking it out from CVS.

Project overview:

The Api Tooling supports profiles. I need to check if this can correspond to our adopter usage reports.

There are also Batch mode tools: Binary Compatibility Reporting and API Usage Reporting, but I am still in progress to find out how to run them.

Update 2008-03-13: No progress this week. I will try to catch API Tooling developers at EclipeCon next week. They also have a Long Talk on the event.

Update 2008-03-27: I had the chance to meet Olivier Thomann. He explained me a lot about the API Tooling and gave useful advices. It seems that we would not be able to use API Tooling in the way we use our adopter API scannages. The concept of API Tooling is different. Instead we can compare for binary and source breakages between WTP releases, e.g. between 2.0.1 and 2.0.2.

Adopting API tooling requires some efforts. It is almost sure that enabling a plugin with API tooling nature will introduce lots of warnings and errors. Rules and filters must be established within the code to prevent this warnings to appear.

Other business?

  • Annoucement: Kaloyan has accepted a position on the WTP PMC
will focus on user experience for JavaEE tools, JavaEE aspects
  • David: we need to change how we generate our javadoc in the build -- project by project, or component by component.
Tim has volunteered to do something for the server project, and recommend to others

Teams Status and Focus for Coming Week

Source Editing

  • Ongoing triaging of incoming bug reports
  • Working on updating bug backlogs
  • Triaging remaining 3.0 requirements and targeted bugs

Server Tools

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing bugs.
  3. Planning for M7.

Java EE

Dali JPT

  • JPT 2.0
    • Released new Editor for persistence.xml
    • Completed Java to JPA project conversion support
    • Working on:
      • Project Explorer contribution
      • XML defaults and validation
      • EclipseLink support


  • Feature exceptions
  • Bug Fixes


  • We will be changing the way we generate source features/plugins
See bug 132094 for details, implications, and links to more info.


  • Branching Strategy
In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well. We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.
  • Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well
  • This Week's Smoke Test Results
WTP Smoke Test Results R30
Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
PMC Candidate Review Request Checklist - See the updated PMC Review document with attention to the "How To Prepare a PMC Defect Candidate" section
Adopter Migration Information for WTP 2.0 - Please add any details for your component.
  • Website
Documentation on Setting up your system for Web Tools Web site development and Using Web Tools Phoenix PHP templates is on the wiki at Web Tools Web Site Development.
  • Bug Day
Monitor and participate in Bug Day if you would like.
Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in IRC
Current WTP Bug Day bugs (~53)

Bug Backlogs

All Untriaged WTP Bugs (Graph)
All Untriaged WTP Bugs (~227)
All WTP Verified, Not Closed Bugs (Graph)
All WTP Verified, Not Closed Bugs (~159)
All WTP Resolved, Unverified Bugs (Graph)
All WTP Resolved, Unverified Bugs (~1532)
All WTP Defect Backlog (Graph)
All WTP Defect Backlog (~3168)
All WTP Future Bugs (~166)
All Open WTP Bugs with Patches Attached (Graph)
All Open WTP Bugs with Patches Attached (~229)
All API Requests (~9)

Back to WTP Meeting Archives

Focus on Backlog and Quality metrics (Neil)

Current Focus Item
  • Options are
  • Target bug for a release or "future"
  • Mark as Invalid or Wont Fix
Upcoming Focus Item
Past Focus Items
  • Invalid - Enhancement does not fit with the scope of the project or is already implemented.
  • helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.
  • Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.
  • Before July 1st, 2007 - 21
Where did they all go?
  • Minutes:
Neil: will focus on untargeted enhancements again after M7

Back to the top