Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseLink/Development/DevMeetings/20081015

EclipseLink Development Meeting 20081015

15 Oct 2008 Minutes


Attendees:

Krogh Peter;
Twelves David;
O'Brien Michael;
Norman, Michael;
Ware Tom;
Meswani Mitesh;
Hauge Neil;
Gwin Eric;
Sapir Rick;
Clarke Doug;
Striffler Roger;


Updates: Sdo spec, and TCK tests - require # of tests passing

Q) can we claim compliance for the SDO spec if it is not ready for dec 9 A) we will not be 2.1.1 compliant until the SDO spec is complete.

Jaxb - no updates

Dbws - will provide highlight/link to status page - optimistic locking and testing are pending

1.0.2 Bugs - 247511 is being looked at

Review - 248858 - regression since TopLink Action: need to assign 248858

247735 - Blaise, was discussed at a conference, Matt has a corresponding bug 249339 for JAXB that is related - issue is fixed only in JDK 1.6 Action: David: - will follow up with Blaise

246317 - needs to be assigned

Static initialization may inadvertently share between EntityManagers


Repository upgrade to 1.5: - Mike N. Will remove this issue

Eric: Build Status: Version class changes done, reviewed (including on Maven) by Tom, Mitesh - only for trunk, not in 1.0.2

Q) checked in derived objects - must remove. - we could use a manifest-only eclipselink.jar that would be static

- examples, we should capture issues on the examples processes wiki page /EclipseLink/Development/Examples

- Eric to add 2 new sections to the html page, dbws, dbws-util

Bug DB usage: - Tom has volunteered to triage incoming bugs - use "performance" in the keyword field - see proposed link to guidelines in EclipseLink/Development/Bugs - enhancement bugs are reviewed but no target is set unless it is urgent - Procedure Note: if developers see trivial issues like spelling, unused imports - then do it as part of your transaction. Vs running a tool for a wide sweep would cause merge conflicts and need to be planned.


Neil: whiteboard status could mark "trivial_fix/patch" as trivial does not work for "simple fix" Simple_fix, patch_supplied

Back to the top