EclipseLink/Development/DevMeetings

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 November 18, 2010

11 am EST, Thurs November 18, 2010

Release Planning

• 2.1.2
  • M1
    • Sept 29th
  • Stream Closed
  • Suggested release
    • Dec 2nd 2010
  • Release Mid Nov
• Future Release Planning starting
  • 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 2 (func freeze) (Indigo M4 - Dec 13th)
    • 2.2 Branch - Dec 3 (post func freeze)
    • 2.2RC1 - Dec 15 - Hard Code Freeze
    • IPLog and Release docuware - Dec 15, 2010
    • 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

Nov 13 - Nov 19, 2010:

• Nightly Results (Updated on 2010-11-18)
  • trunk - 4 new failures with foundation test-not-lrg, some hardcoding with DB (old database) URLs in the those test cases - fixed; JPA on WLS MAIN failed, seems WLS problem - investigating; (the last build is 2010-11-17)
  • 2.1.2 - no new build (the last build is 2010-11-04)
  • 2.0.3 - 4 new failures with foundation test-not-lrg, some hardcoding with DB (old database) URLs in the those test cases - fixed (the last build is 2010-11-08)
  • 1.2.1 - no new build (the last build is 2010-10-05)
• Testing
  • JAXB 2.2 TCK on trunk/2.1.2 (eclipselink-2.2.0.v20101022-r8382) - not getting consistent results as Dev's - re-configured and now working correctly; several bugs will be filed today
  • x64 testing - complete
• Test Dev
  • Cache Co-ordination - automation plan in progress (early stage)
• Test Infrastructure
  • Migration of databases and nightly automation to new hardware - complete
  • JPA 1.0 Glassfish TCK JavaSE -- down due to hardware migration - working on restoring
  • Performance tests -- down due to hardware migration. - working on restoring
  • SDO TCK -- down due to hardware migration. - working on restoring
  • Code Coverage -- building the code failed -- related to hardware migration.
• This week
  • Automate new cache co-ordination example written by Dev
  • Publishing nightly results - will tackle after all nightly tests enabled
  • To do - test 64-bit app servers...
  • Re-enable nightly tests

Build

November 18, 2010:

• Milestone Releases
  • 2.2.0 M5 (v20101117-r8503)
• Move to generic build ID
• Fix p2 publication
  • child prepositories appear properly formed, but new children seem not to be recognized
  • Needs to be fixed for Indigo contributions.
  • Holding on to 2.1 and 2.0 until 2.1 opens up again. (trunk complete).
• "Host" publication script
  • 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
• Fix Maven dependency publication
  • Complete on trunk.
    • Need to activate runtime dependency publication (javax.persistence active)
  • Migrate to older branches?
    • 2.1: don't overwrite javax.persistence any more (2.1 - frozen)
    • 2.0: probably not necessary other than for consistency
• EclipseLink Summit Items to review:
  • Move to new build? (drop ant)
    • Investigation in progress.
      • Preliminary Pros/Cons table in progress
      • "Issues needing resolution" list will be appearing soon.
  • Rename build.xml and build.properties (260428)
    • will rename to: build.xml->antbuild.xml build.properties->antbuild.properties
    • in progress (awaiting opening of 2.1)

Fixed Bugs: 303621, 330494

JPA

Nov 18, 2010:

• Bug Fixes
• 2.2.0
  • Additional Criteria
    • http://wiki.eclipse.org/EclipseLink/Development/AdditionalCriteria
  • Multiple Database support
    • Composite EMFs
    • Wiki pending
    • Target Release depends on final scope
  • Append to Create table string - Checked in
    • http://wiki.eclipse.org/EclipseLink/DesignDocs/214519

• • OSGi
    • Bug fixes and updates to facilitate testing
    • Gemini contributions

DBWS

DBWS Development

2.2

• Prioritizing DBWS backlog
  • 329435 - DBWS does not handle %ROWTYPE mix of PL/SQL types and JDBC Advanced types
    • Based on investigation, this is a non-trivial fix and would be risky to fix in 2.2. Pushing out to 2.3
  • Expand DBWS server tests to run on Glassfish, JBoss, WAS

Future

• DBRS
  • Look at role of DBWS in RESTful web applications
• Bug 322950 Investigate distributed transactional support via WS-AT (testing exercise)
• Database web service call-out utility
  • New feature to allow code running on a database (eg. in PL/SQL module) to invoke a JAX-WS service. The input to the process is the WSDL for the Web service, along with any additional information necessary to locate and invoke the service (hostname, port, etc.)

SDO / MOXy

2.2.0

• MOXy annotation and external metadata support
• Dynamic JAXB - Bootstrap from MOXy XML file
• Cleaning up remaining bugs associated with these features - on track for 2.2 RC

2.3.0

• JBoss: Implemented a 2.1 solution to detect a redeploy event using MBean notification listeners
  • Need to migrate to use full core MBean solution on these platforms
• JPA/JAXB RESTful web services
  • Provide means of exposing JPA entities through a RESTful service
  • Discussing how to integrate this into the existing DBWS component.
• MOXy User Guide evolution
  • Updating user guide content based on new annotations and metadata support
• Eclipse Dali
  • Discussion with Dali development team to provide JAXB/MOXy support based on annotations or external metadata

EclipseLink Incubator

EclipseLink/Development/Incubation

• 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: http://wiki.eclipse.org/EclipseLink/UserGuide/JPA
• Need input/outline for additional guides (moxy, dbws, etc.)
  • MOXy: http://wiki.eclipse.org/EclipseLink/UserGuide/MOXy

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports