Revision as of 10:52, 15 July 2010

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 Jun 10, 2010

11 am EST, Thurs Jun 10, 2010

Ad Hoc

• Intermittent failures on build machine: what good are the reports if we can't trust them?
  • Different test failure each time.
• EclipseLink Summit Wrap-up
  • Comment on notes from Thursday sessions to ensure we captured all the important points (dev mailing list)
  • Open issues will be added to this agenda
    • This Week - Looking at some of the build issues.
  • Process topic of contribution log - Please make sure all new code in 2.1 has proper header and dates
    • a sweep of 2.1 was done last week.

Release Planning

• 2.1.1
• 1.2.1
  • requests to shut this down...

• 2.0.3
  • June/July

• Future Release Planning starting
  • 2.2 - December 8th, 2010 - http://wiki.eclipse.org/EclipseLink/Development/2.2
    • 2.2M1 - July 21
    • 2.2M2 - August 19
    • 2.2M3 - September 22
    • 2.2M4 - October 20 - Functional Freeze.
    • IPLog and Release docuware - end of October
    • 2.2RC1 - November 3rd, 2010
    • 2.2RC2 - November 17th, 2010
    • 2.2RC3 - Novemeber 24th, 2010
    • 2.2 Release - December 8th, 2010
  • 2.3 (Indigo) - June 22nd, 2011 - http://wiki.eclipse.org/EclipseLink/Development/2.3

QA

July 9-15, 2010:

• Nightly Results
  • trunk - 2 new failures in oxm-lrg - investigating, failures with osgi-srg - fix checked in; DBWS failures with Oracle DB
  • 2.1.1 - failures with osgi-srg - should be fine tomorrow.
  • 2.0.3 - no new build (the last build is 2010-07-01)
  • 1.2.1 - no new build (the last build is 2010-06-29)
  • 1.1.4 - no new build (the last build is 2010-06-16)
• Testing
  • SDO 2.1.1 TCK for main/2.1 - 2 failures - dev is working on this.
  • EL 2.1.1 DB Certification manual testing (dbs not included in nightly DB certification runs).
  • JPA 2.0 tests passed on WAS 7.0.0.11 with JPA 2.0 feature pack
  • Test Dev 2.2/2.1.1 - EL 2.1 Advanced Query:
    • Fetch Group test dev - 90% ETA July 16 - code not checked in; most of code had been reviewed -- only one test suite need to be changed based on feedback; all tests migrated to run on servers; will be enabled to run nightly on WLS, WAS. JBoss, Glassfish
    • Enhancements to test fwk to support testing multiple persistence units - currently the cacheable tests use Multiple PUs, but we need to investigate if it is working as expected.
  • test fwk enhancements
    • DB Certification automated testing enabled on 2.0 stream - runs on Saturday
    • Update Nightly Testing WebSphere installation to fixpack11 and JPA2.0 and OSGI feature pack for AS and ND both
    • Minor tweaks on the feature - "Automatically kill overdue process and send out an email alert" to have more informative email message
    • Updated JPA 2.0 TCK to jpatck-2.0_15-Jun-2010.zip
    • Setup and ran JPA 1.0 CTS with WLS PS3 and EclipseLink 2.1.0 via replacing the javax.persistence_1.0.0.0_2-0-0.jar with javax.persistence_1.0.0.0_1-0-2.jar
• Bugs
  • Filed
  • Fixed
• This week
  • Multiple Persistence Units
  • Fetch Groups test dev - migration and dev based on new TCs checked in by dev
  • osgi/Gemini investigation (testing focus)
  • Review and target bugs for 2.1.1

Build

• Helios Released
  • EclipseLink 2.1.0.v20100614-r7608 in Helios repo
• Milestone Releases
  • none
• Working on way to detect jarnames of a dependency. Part of 312437.
  • ant task debugged, reviewed by Mike Norman, and merged.
  • need to hook into build for bnd detection.
  • in future can be used to detect jars to use for latest Orbit drops, and other dependency checks.
• EclipseLink Summit Items to review:
  • Move to PDE build? (drop ant)
    • Advantages: get many features now have to 'hack'
    • Disadvantages: tied to someone else's process. May not work with our versioning. Web distributions, etc.
    • If we decide to drop ant support will need to plan phase-out, and investigate PDE capabilities further.
  • Rename build.xml and build.properties (260428)
    • what to rename to? antbuild? eclipselink? suggestions?
• Review process for build bugs?
  • Future direction of build?
    • Creating Wiki page to capture open issues and help plan improvements (It will also capture bugs below)
      • Review and vote? on: 260428 273911 279176 295071 298286 298790 299060 301698 (303006 close?) 303621 303630 305386 308919 309853
      • Once created can revisit review process.

Fixed Bugs:

JPA

June 10 2010:

2.1.0

• Advanced JPA config
  • Dynamic persistence
• Advanced JPA Querying
  • Fetch groups still in progress
• OSGI
  • Initial Gemini Integration done
    • No Weaving
• Bug Fixes

DBWS

DBWS Development

2.2

• Target DBWS support for Glassfish, JBoss, Websphere
  • Determining how to create a fragment/bundle for DBWS that can installed as an update into Glassfish.
  • Assuming user will be able to select this fragment as an optional update
• Sparse Merge Support
  • EclipseLink2.2 goals reviewed with PM
  • Investigating how to create a dynamic entity which contains a partial FetchGroup
  • Reviewed isSet() behaviour used in Dynamic Persistence
  • Building on top of Fetch Group feature introduced in EclipseLink2.1 - identifying usecases and setting up initial Proof of Concept

SDO / MOXy

2.1.1

• MOXy externalized metadata
  • JBoss: Investigating how to detect a redeploy event using MBean notification listeners
    • Current solution was causing an issue if the context loader changed

2.2.0

• Targetting deprecation of existing MOXy deployment.xml
  • Provide full support through external metadata file and annotations.
• MOXy External Metadata support
  • Identify entries in deployment.xml that are currently not represented in external XML file.
• MOXY Dynamic Persistence
  • Provide ability to bootstrap from external MOXy XML file
• SDO Server testing
  • Running automated SDO server tests against JBoss, WAS, WLS app servers.
• Feature work: Platform integration
  • Demo: Use EclipseLink JAXB when running JAX-RS RESTful web service (based on Jersey RI). Demonstrates ability to marshal to JSON as well as XML documents.

EclipseLink Incubator

EclipseLink/Development/Incubation

• EclipseLink/Development/Incubator/Extensions
  • MaxDB work in progress
• Time to create separate sub-project for incubator
  • Increase community of committers
  • Try out GIT & eGit/jGit tooling in incubator?

Documentation

• New EclipseLink documentation plan: Documentation Requirements and Build Proposal
• Continuing to build/port JPA content to new JPA guide: [1]
• Need input/outline for additional guides (moxy, dbws, etc.)

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports