Revision as of 13:38, 23 November 2009

Dial In Info:

• please contact 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 Nov. 26, 2009

Meeting format:

• Milestones
• Work Allocation
• Completed
• @Risk

11 am EST, Thurs Nov 26, 2009

• remove .settings/org.eclipse.jdt.core.prefs from SVN version control

Ad Hoc

• move the TestFramework to separate project?

Milestones

• Google calendar above.

• 1.1.3 Patch Set - Released Oct 9/09
• 1.2.0 - Released Oct 23/09
• 2.0.0 Weekly Milestones until release
  • M10 - released Oct 19/09
  • M11 - released Oct 26/09
  • M12 - released Nov 02/09
  • M13 - scheduled Nov 05/09 (javax.persistence 2.0 renamed)
  • M14 - scheduled Nov 09/09
  • M15 - scheduled Nov 16/09
  • RC - scheduled Nov 23/09
    • Branch? at this point
  • GA - scheduled Dec 10th
• 2.0.0 Release - GA Scheduled Dec 10/09

• Helios - Annual release - June 24/2010
  • M1 - August 21/09: Included EclipseLink 1.1.3 M1
  • M2 - October 2/09: Included EclipseLink 1.1.3 RC1
  • M3+1 - November 9/09: targeting inclusion of EclipseLink 1.1.3 Release
  • M3 - November 13/09: Available
  • M4+1 - December 14/09: targeting inclusion of EclipseLink 2.0.0 GA?
  • M4 - December 18/09: Available

• Galileo SR2 - February 26th/2010
  • RC1+0 Jan 18/10: EclipseLink 1.1.x (latest Milestone or Release)

QA

• Continuing to close down on EL 2.0 testing this week; targeting Nov 25 for completion
  • Functional Testing 95% complete; Certification testing 35% complete
  • Expecting all test results for DB cert today and will triage tomorrow.
• Continue to work with Eric as needed on builds

Build

• Milestone Releases
  • 2.0.0 M13
  • 2.0.0 M14
• Build rework for "Release" of javax.persistence 2.0
  • fixup for maven. Not treated as any third party jar (still part of org.eclipse.persistence)
  • need to fix verion to static
  • update Maven info to create as sepatate entity - needs to be run once then commented out.
• Maven submissions need to include dependecy info for artifacts (279177)
  • Currently investigating requirements
• Test component build cleanup
  • Complete "Build rework" on these components (260295).
  • Restructure to allow testing to *not* rebuild product jars (293032)
    • Currently detecting and setting paths based upon jar availability - use same targets.
      • Blaise has stated preference for explicit targets for use of eclipselink, or OSGi
      • The assertion has also been made that tests should neither build nor run using classes.
      • Is this agreed by all?
  • Need shippable testing artifacts (R2).
• Helios build integration (293034) - Holding (Post 2.0.0 Release)
  • Local transaction to:
    • update "features" for Helios
    • add jar signing, and packing
  • Cannot merge until javax.persistence_2.0_preview jar becomes javax.persistence_2.0.0*.jar (targetted for Nov 2)
• jpa.test10 Suite
  • Explore possibility of using eclipselink.jpa.test from 1.1.3 as a way to certify javax.persistence 1.0 backward compatability in EclipseLink 2.0.x
    • All tests now compiling with trunk
    • working on running them.
• Working on changing tests to use "forkmode=once" (290177)
  • In progress

Fixed Bugs:

JPA

Completed

• The 'final' API updates are checked in.
  • Jar still called 2.0_preview.
  • Targetting chaing thins for Nov 6th drop
• closing in on 0 failures with JavaSE tck results

Work allocation

• JPA 2.0
  • Triage of bugs
    • Review submitted patches

DBWS

• Completed
• Work allocation
  • move to core Dynamic Persistence
• DBWS

SDO / MOXy

• Work Allocation
• Completed

• SDO
  • EclipseLink1.1.1 fully passes the SDO2.1.1 TCK on JDK1.5 and JDK6.
• MOXy
  • EclipseLink2.0: targetting JAXB 2.1.x compliancy.

287296 SDO: Need to be able to compile against SDO 1.0 Jar 287690 JAXB - exception is thrown when it shouldn't be (xmlvalue annotation on enum) 287855 Exception unmarshalling from XmlStreamReader with class to unmarshal to specified 288131 Unmarshalfrom XMLStreamReader stress test causes StackOverFlow Error 288297 NPE unmarshalling from StreamReader if startDocument isn't triggered 286316 SDOProperty should set schema type of BinaryDataMapping to base64Binary 286872 AnnotationsProcessor should use new "isRequired" API

EclipseLink Incubator

EclipseLink/Development/Incubation

• SDO DAS Update - Close down?
• EclipseLink/Development/Dynamic
• Proposed EclipseLink/Development/Incubator/Extensions

Bug Status

Bug reports

Foundation and JPA

Open Bugs

Bugs By Target and Priority

Resolved Bugs

Resolved Bugs

New Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports

General Issues

• Running JPA in JavaSE mode on trunk
  • Issues due to jar signing and split javax.persistence package
  • If you run in Java SE with the javax.persistence 1.0.0 jar shipped with EclipseLink and eclipselink.jar you will get security exceptions on our trunk stream (but not our released streams)
  • We solve this in our testing with an unsigned version of the javax.persistence jar. We may have to consider a similar strategy for our "installer-zip" distribution.
• SPI defaulting
  • We provide a number of service advertisements in META-INF/services of eclipselink.jar
  • It is possible that installing eclipselink.jar to make use of one service (e.g. JPA) will transparently change the provider of another service (e.g. JAXB) to use EclipseLink if the user has not explicitly specified their service providers.
• Wiki site update
  • Ensure that wiki site reflect state of feature
• Location of Docs moving forward
  • where to put 2.0 documentation.
  • breaking down features into smaller pages.
  • potential clone of wiki.

Upcoming Issues

The following items require discussion but are not yet at the stage where a solution can be proposed.

• EclipseLink/Development/Examples: Strategy for the development and maintenance of examples
• EclipseLink/Development/OSGi: Strategy for delivery of OSGi/Equinox bundles
• EclipseLink/Development/JPA 2.0: Strategy for the concurrent development of JPA 2.0 while maintaining JPA 1.0 usage
• EclipseLink/Development/Spring: Strategy for using EclipseLink within the Spring Framework

Minutes from Past Meetings

• Feb 18, 2009
• Feb 11, 2009
• Feb 4, 2009
• Jan 28, 2009
• Jan 21, 2009
• Jan 14, 2009
• Jan 7, 2009
• 2008
• 2007
• Previous minutes

References