Revision as of 11:59, 25 February 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 Feb 25, 2010

11 am EST, Thurs Feb 25, 2009

Ad Hoc

Release Planning

• 1.1.4: Not yet scheduled - Planned final patch for 1.1.x stream
  • wait for community to request.
• 2.0.2: Proposed date: April 21st
• 2.1 Helios
  • http://www.eclipse.org/projects/project-plan.php?projectid=rt.eclipselink
• Galileo SR2 - February 26th/2010
  • RC1+0 Jan 18/10: EclipseLink 1.1.3 (latest Milestone or Release)
    • 1.1.3 has been put into SR2

QA

Feb 19 - 25, 2010:

• Last week
  • Monitor and triaged nightly tests:
    • 1.1.4 - good
    • 2.0.2 - good (WAS Oracle custom features tests failed - fixed; SQL Server 2008 nightly hanged (intermittent failure)
    • 1.2.0 - good
    • trunk - good (DBWS examples on WLS didn't run properly - fixed)
  • Pessimistic Locking Extended Scope - test checked in but not enabled - 303360 - dev bug; also need to review the comments in source code
  • MOXY (trunk) - using Oracle xmlparser still has issues - 6 errors - bug 303918
  • Fixed DBWS nightly test failures - env issues
  • investigated JDK15 issues (trunk) - unclean db
  • Fixed JPA/Glassfish recent nightly test failures - minor test script changes
  • Investigated Glassfish/Derby test failures - concluded that func failure related to Glassfish/Derby combo -- tests passed on WLS/Derby and Glassfish/Oracle DB - bug 290302
• This week
  • EL 2.1 - osgi, advanced querying
  • Fix Bugs
  • Test infra doc updates
  • Builds - our nightly tests sometimes can't get the eclipselink.zip file (from website) at the designated time....

Build

• Milestone Releases
  • 2.0.1 RC1
• Test component build cleanup (Holding)
  • Restructure to allow testing to *not* rebuild product jars (293032)
    • Will use "static targets" as discussed in meeting last week (297217).
    • Tests will not compile when run target called.
      • merged partial work to update standards.
      • migration work for test projects, currently priority 2
  • Need shippable testing artifacts (R2).
• Helios build integration (293034)
  • Need to do p2 consolidation work to manage multiple versions in a single update location.
    • investigation composite repositories
    • currently determining if existing ant tasks designed for use within Eclipse can be utilized externally.
• jpa.test10 Suite - Holding
  • 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, 83% success rate on Test run.
    • Awaiting review by Tom or Peter of test results (still).
  • Need "project name" assuming this gets running 100%

Fixed Bugs:

JPA

Feb 18 - Feb 25

2.1.0

• Advanced JPA config
  • attributeName
    • Dynamic persistence requirment
• Advanced JPA Querying
  • wiki started with prioritized feature list (http://wiki.eclipse.org/EclipseLink/Development/2.1/AdvancedJPA_Queries)
  • Prototype of FUNC support in JPQL.
  • Uncovered bug in TRIM, being worked on simultaniously
    • available on bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=300512
• OSGi
  • Investigation delayed somewhat
  • Will start investigation tomorrow.
• Bugs with Votes

DBWS

DBWS Development

2.0.2

• 303331 Currently throw NPE for PL/SQL procedure with argument defaults. Need to handle this more gracefully

2.1.0

• Scoping out potential EclipseLink feature work
  • Support for advanced PL/SQL datatypes (records, collections, mixture of the two) as arguments to Stored Functions
  • Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)
• DBWS (JAX-WS) support on multiple platforms (JBoss, WAS)

SDO / MOXy

2.0.2

• 301062 MOXy - JAXB: Issues with multiple XmlElementDecl with same QName and different scope
• 302481 Account for XMLStreamReader returning both null and "" for no namespace
• 303631 JAXB - incorrect date conversion from XMLGregorianCalendar with schemaType set to date
• 303692 JAXB - static final attribute fields are ignore during schema generation but should make fixed attributes
• 302167 XMLBinderBasicTests are failing with Oracle's Xmlparser

2.1.0

• Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
• MOXY Dynamic Persistence Design
• JAXB2.2 Compliance
  • JAXB2.2 CQs approved (API, RI, XJC).
    • Blaise has been nominated as an Orbit committer, in readiness for contributing the JAXB2.2 binaries.
  • Also need to submit JAXB2.1.12 jars to Orbit (CQs previously approved for Helios)
• Continued improvements to MOXY marshalling/unmarshalling performance

Dynamic Persistence

Dynamic Persistence

• 303651 Issue raised on forum with dynamic entities not having their attribute-change-tracker properly setup after the first entity transaction commit call

EclipseLink Incubator

EclipseLink/Development/Incubation

• EclipseLink/Development/Incubator/Extensions
  • FetchPlan incubator active
    • Doug requesting help.
  • Please provide feedback on Proposal for lowering barrier of entry for new database platforms

Documentation

• Working on automated doc build process (Rick & Eric)
  If not possible, Rick is working on an automated localized doc build process, and would simply post the daily doc builds
• Updated Documentation Requirements and Build Proposal
• Several "chapters" currently stored in XML. More to come once the production/build process is finalized.
• Need discussion about how the strategy we are using for User Documentation compares to the wiki-based strategy we are using for developer documentation and whether there is merit to changing the way we do developer documentation. This discussion should wait until we have used found all the issues with our User Documentation Strategy.

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