Revision as of 10:00, 2 September 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 August 19, 2010

11 am EST, Thurs August 19, 2010

Ad Hoc

• Discuss 2-part IPLog process for Bug and Attachment searchable Flags - mobrien 20100806
• Process topic of contribution log - Please make sure all new code in 2.1.1 has proper header and dates

Release Planning

• 2.1.1
  • GA (Helios SR1) Aug 27th
• 1.1.4
  • 10 bugs closed in 1.1.4
  • No open bugs
  • RC1 - Aug 13th

• Future Release Planning starting
  • 2.1.x
    • Helios SR2
      • RC1-4 - Jan 17,31, Feb 7, 14
      • GA - Feb 25
  • 2.2 - December 8th, 2010 - http://wiki.eclipse.org/EclipseLink/Development/2.2
    • 2.2M1 - July 21 (Indigo M1)
    • 2.2M2 - August 19
    • 2.2M3 - September 22 (Indigo M2 - Sept 27th)
    • 2.2M4 - October 20 - Functional Freeze.
    • IPLog and Release docuware - end of October
    • 2.2RC1 - November 3rd, 2010 (Indigo M3 - Nov 8th)
    • 2.2RC2 - November 17th, 2010
    • 2.2RC3 - Novemeber 24th, 2010
    • 2.2 Release - December 8th, 2010 (Indigo M4 - Dec 13th)
  • 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

Aug 20 - Aug 27, 2010:

• Nightly Results
  • trunk - no builds (last build Aug 19)
  • 2.1.1 - no builds (last build Aug 17)
  • 2.0.3 - no builds (last build Aug 23)
  • 1.2.1 - oxm and jaxb tests failed to run with JDK 1.5 - investigating (the last build is 2010-07-30)
  • 1.1.4 - no new issue (the last build is 2010-08-13)
• Testing
  • 2.1.1
    • Completed certification and manual tests; continue to monitor nightly
  • 1.1.4
    • Nightly automated tests triaged
    • Manual testing in progress ~ 90% complete
• Test Dev
  • osgi/Gemini investigation in progress
  • WAS script changes -- void hard coding in WAS python scripts - 90% complete
• Test Infrastructure
  • Enhance documentation
• Bugs
  • Filed:
  • Fixed:
• This week
  • Test fwk changes - avoid hard coding in WAS python scripts - ongoing
  • MBeans testing against JBoss/WAS/Glassfish
  • Investigate automating the "setting of EclipseLink as default PP" in a WebLogic domain
  • osgi/Gemini investigation (testing focus) - in progress
  • 1.1.4 testing

Build

• Milestone Releases
  • 2.1.1 GA - Aug 27th (Tom)
• Move to generic build ID
  • Potential issues with regards to Legal (Signing permissions, check-in access)
    • Modifying build to compensate:
      • signing done at milestone promote.
      • remove artifact check-in (and the eclipselink.jar and eclipselink-src.zip from SVN repos)
      • publishing will need to be done in separate cron task
• EclipseLink Summit Items to review:
  • Move to new build? (drop ant)
    • If we decide to drop ant support will need to plan phase-out, and investigate PDE capabilities further.
      • Investigation in progress.
        • Preliminary Pros/Cons table in progress
  • Rename build.xml and build.properties (260428)
    • will rename to: build.xml->antbuild.xml build.properties->antbuild.properties
    • in progress

Fixed Bugs:

JPA

July 22 2010:

• Bug Fixes
  • Submitted Patches and voted bugs for various stream
  • "Low hanging fruit"
  • Several bugs that did not make 2.1.1 cutoff (will be checked into 2.1.2 stream)
• 2.2.0 planning will begin soon

DBWS

DBWS Development

2.1.1

• DBWS in OSGi environment
  • Created a OSGi fragment bundle which a user can drop into Glassfish to access DBWS runtime services.
  • DBWS in Equinox OSGi environment with Jetty
    • Submitted final fix to 2.1.2 stream.

2.2

• Prioritizing DBWS backlog
  • DBWS Sparse Merge Support Bug 322948
    • Building on top of Fetch Group feature introduced in EclipseLink2.1
  • Expand DBWS server tests to run on Glassfish, JBoss, WAS
  • Bug 322950 Investigate distributed transactional support via WS-AT (testing exercise)
  • Bug 322949 Add support for ResultSet metadata at design-time for Custom SQL
    • Investigating how to use a custom SQL parser to extract database metadata.
  • DB-RS
    • Look at role of DBWS in RESTful web applications

SDO / MOXy

2.1.1

• No remaining bugs open for 2.1.1
• JBoss: Implemented a solution to detect a redeploy event using MBean notification listeners
  • Will migrate to use full core MBean solution on these platforms in 2.2

2.2.0

• Targetting deprecation of existing MOXy deployment.xml
  • http://wiki.eclipse.org/EclipseLink/DesignDocs/317962
  • Phase 1 – MOXy annotation equivalent to XML metadata support - Complete
  • Phase 2 – Annotations and XML Support for relevant ORM annotations - Complete
  • Phase 3 - Annotations and XML Support for relevant JPA annotations
    • DiscriminatorColumn, DiscriminatorValue, JoinColumn(s), XmlKey
• Dynamic JAXB - Bootstrap from MOXy XML file
  • Enhanced JAXBContext.newInstance() API to allow user to bootstrap from all three sources (sessions.xml, XMl Schema or MOXy file)
  • Phase 5: Continue annotations test cases
• JAX-RS Integration Demo
  • 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.
• MOXy User Guide evolution
  • Designing new layout to promote specific use cases and examples to users, explaining how to use MOXy to resolve specific issues. Include relevant annotations required for implementation.
  • Some of the reference material available in existing user guide may be ported to JavaDocs to make it easier for users to find and also to simplify maintenance for committers.
  • Will link to JavaDocs directly from main User Guide

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: http://wiki.eclipse.org/EclipseLink/UserGuide/JPA
• 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