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 11:37, 20 January 2011 by Huyen.h.nguyen.oracle.com (Talk | contribs) (→‎QA)

(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 13, 2011

11 am EST, Thurs Jan 6, 2011

Ad Hoc

Release Planning

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
- 2.2RC2 - Jan 12th
- IPLog and Release docuware - Jan 12th, 2010
  - Release review complete
- 2.2 Release - Jan ??, 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

Jan 13 - Jan 20, 2011:

EclipseLink (Updated on 2011-01-20)
- trunk - 1 new failure with foundation not-in-lrg testing - investigating; 1 new failure with DBWS testing - investigating; all spring tests failed with " invalid username/password" - configuration issue, investigating; several new failures with JPA on Derby - investigating; 1 new failure with JPA on H2 - dev investigating. (the last build is 2011-01-20)
- 2.2.0 - no new issue (the last build is 2011-01-19)
- 2.1.3 - no new issue (the last build is 2011-01-17)
- 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
- trunk
  - ...
- 2.2
  - Cache Co-ordination tests need to be completed - RMI
  - GF/EL tip to tip testing -- not started
  - Sybase - limited tesing on JPA
Test Dev
- DBWS Examples on various app servers -- ran in GF, found issues and investigating
- Cacheable and non-cacheable relationships - review complete, sending out list of tests we want to add to be reviewed by dev.
- JAXB Annotation Examples automation -- in progress. Project plan will be sent out for review.
Test Infrastructure
This week
- Triage
- Continue with Test development work
- Remaining 2.2 tests
- Publishing nightly results - on hold until DBWS test impl completed

Build

January 13, 2010:

Milestone Releases
- 2.2.0 RC2 (2.2.0.v20110112-r8804)
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
  - Follow-up discussions will be needed to determine final direction
Rename DBWS Utils to org.eclipse.persistence.dbws.builder
- updated build to package as OSGi bundle
- renamed jar and project
- renamed test projects (eclipselink.dbws.builder.test*)
- updated DBWS feature to include new bundle (do I need to add WSDL and SERVLET bundles?)
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 13, 2011:

2.2 closedown
- potential issue discovered in RC2
  - looking into it now
2.3
- Composite PUs
- MT
- Extensabilty

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.

Dynamic Persistence

Core

answer Rohit's questions on EL-User mailing list (happy with 2.2)

Dynamic JAXB

discussion about expanding public API w Rick, Blaise for DBWS Callout

Dynamic JPA

new JPA 2.0 SPI (PersistenceProviderResolver, PersistenceProviderResolverHolder) makes bootstrapping pure Dynamic JPA (no persistence.xml, no orm.xml) much easier.
- TODO: update eclipselink.jpa.tests(o.e.p.testing.tests.jpa.dynamic.*) to use new SPI

SDO / MOXy

2.3 RoadMap

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