Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Revision as of 10:52, 12 January 2011 by David.twelves.oracle.com (Talk | contribs) (→‎SDO / MOXy)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Dial In Info:

please contact Peter Krogh for dial in information.

The EclipseLink committers have a regular meeting (currently weekly) to discuss ongoing development issues and projects. All interested parties are welcome to attend. If you have any additional items you wished discussed please add them at the bottom of the agenda including a brief description and any relevant links. Alternatively development issues can be discussed on the EclipseLink Dev mailing list.

* When adding agenda items please send an email to the eclipselink-dev@eclipse.org list notifying attendees. This will ensure attendees are aware of agenda items prior to the meeting.

Call Schedule

The calendar is available in the following formats:
iCal,ATOM News Feed,HTML

Agenda Jan 6, 2011

11 am EST, Thurs Jan 6, 2011

Ad Hoc

IPLOG

IpLog wiki page being decommisioned
We will use auto generated IpLog
set iplog dropdown to + in bugzilla
- On the bug: If contribution is in a comment on the bug -
- On the patch file: If contribution is in the patch
  - NOTE: you must set iplog to + ON THE USER SUBMITTED PATCH - not the one that was attached by a committer. Even if the patch is obsolete. (Unless no ip from the patch was used in the final submition)
http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Using_the_Automated_IP_Log

Release Planning

2.1.2
- Final bits built
- Final bits available for download
- Webpages, javadocs, release notes etc... over the next few days.
2.2 - January ??, 2011 - http://wiki.eclipse.org/EclipseLink/Development/2.2
- 2.2M1 - July 21 (Indigo M1 & M2 & M3)
- 2.2M2 - August 19
- 2.2M3 - September 22
- 2.2M4 - October 20
- 2.2M5 - Nov 18
- 2.2M6 - Dec 9 (func freeze) (Indigo M4 - Dec 13th)
- 2.2 - Dec 3 (post func freeze)
- 2.2RC1 - Branch - Dec 15 - Showstopper mode
- IPLog and Release docuware - Dec 15, 2010
  - On track
- 2.2RC2 - Jan 4, 2011
- 2.2 Release - Jan 18, 2011
2.3 (Indigo) - June 22nd, 2011 - http://wiki.eclipse.org/EclipseLink/Development/2.3
- Indigo M5 - Feb 7
- Indigo M6 - March 14
- Indigo M7 - May 2
- Indigo RC1-4 May 16,23,30 and June 6
- Indigo GA - June 22

QA

Dec 30 - Jan 06, 2010:

Nightly Results (Updated on 2011-01-06)
- trunk - 4 new failures with JPA testing (ProxyAuthentication on both javaSE and javaEE) - investigating; several new failures with jaxb and oxm (seems relating the configuration with xml parser) - investigating; DB certification testing with JPA on all DB met "Forked Java VM" issue - is debugging with developer; (the last build is 2011-01-06)
- 2.2.0 - 2 new failures with JPA on javaEE - developer is looking at them. (the last build is 2010-12-31)
- 2.1.3 - 4 new failures with JPA testing (ProxyAuthentication on both javaSE and javaEE) - investigating (the last build is 2011-01-05)
- 2.0.3 - no new build (the last build is 2010-11-25)
- 1.2.1 - no new build (oxm and jaxb didn't run properly, there are some compile error with testing framework - investigating by QA) (the last build is 2010-11-26)
Testing
Test Dev
- EL 2.2 - cacheable and non-cacheable relationships - reviewing current tests - in progress
Test Infrastructure
- Added 2.2 branch to nightly automation
This week
- Automation of JavaDoc examples for JAXB Annotation
- Extend DBWS testing - discussed with developer; get DBWS examples running on various app servers
- 2.2 Features – cacheable and non-cacheable relationships - complete tests review
Backlog:
- Sybase hang issues -- found 99% of cause with dev's help -- need to close the EntityManagerFactory for test suites -- still need to figure out how to fix in test infra.
- Publishing nightly results - on hold until DBWS test impl completed

Build

December 16, 2010:

Milestone Releases
- 2.2.0 M6 (v20101209-r8662): Promoted to Indigo M4
- 2.1.2 Release (v20101206-r8635)
2.1.3 Open
- First nighlty was successful.
New Build
- Working on completing evaluation
  - mock-up end-to-end build (materialize & build core, a core feature, publish (p2, maven, and a zip) and test
- Am targeting next week for presentation. (what does buckminster mean for us)
  - Seem to be on-track
  - Follow-up discussions will be needed to determine final direction
"Host" publication script - complete
- refinements to publish process for Oracle and other "hosted environment" test result publication
- script to grab results from specified location and push to Eclipse download server
Rename build.xml and build.properties (260428)
- will rename to: build.xml->antbuild.xml build.properties->antbuild.properties
- Targeting Beginning of year

Fixed Bugs:

JPA

Jan 6, 2011:

Bug Fixes
2.3
- Composite PUs
Begin additional Planning for 2.3

DBWS

DBWS Development

2.3

Build environment
- Plan to include DBWS feature in SDK bundle made available in p2 repository
Prioritizing DBWS backlog
- Database web service call-out utility
  - Working on generation of Java Stored Procedure from WSDL file
  - PoC next step - use hand-coded JavaSP to test running in OJVM environment
- Expand DBWS server tests to run on Glassfish, JBoss, WAS
- Eclipse IDE based integration for the DBWS tooling
- Creating DBWS utils bundle for Dali testing - jar will be renamed.

SDO / MOXy

2.3 RoadMap

JPA/JAXB RESTful web services
- Provide means of exposing JPA entities through a RESTful service
- Debugging and fixing issues raised when testing JAX-WS TCK using EclipseLink JAXB in Glassfish server. Plan to bundle MOXy with Glassfish install in next release
Performance
- Need to review current JAXB performance metrics, also memory footprint.
MOXy User Guide evolution
- Working with Rick S on new MOXy user guide
Eclipse Dali
- Discussion with Dali development team to provide JAXB/MOXy support based on annotations or external metadata