Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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.gifiCal,Xml.gifATOM News Feed,Html.gifHTML



Agenda Apr 8, 2010

11 am EST, Thurs Apr 8, 2010


Ad Hoc

Intermittent failures on build machine: what good are the reports if we can't trust them?

EclipseLink Summit: http://wiki.eclipse.org/EclipseLink/Development/Summit

Release Planning

QA

May 7 - May 13, 2010:

  • Nightly Results
    • 2.1 - 1 FL test failure Oracle 11.1.0.7 - investigating;
    • 1.1.4 - no recent builds : no issues
    • 2.0.3 - no issues (last build May 6)
    • 1.2.1 - frozen: no issues (last build May 6)
  • Last week
    • Fixed Bugs
      • 312285 all tests in jpa jpaadvancedproperties model failed on GlassFish V3 only in trunk
      • 312689 Need to give correct schema name for namespace in seesions.xml for JPA testing
    • Enable SDO server tests to run nightly on all app servers - WLS running nightly; still debugging WAS and JBoss failures
    • Informix - bugs filed, JPA hang - not worked on last week
    • EL 2.1 Advanced Query
      • Downcast - test spec - 100% - needs to be reviewed
    • EL 2.1 Advanced JPA Config - test plan - 90%
    • JAXB 2.2 TCK on JDK 1.6 issues - resolved.
    • Enable Bean Validation tests - 100%
    • test fwk enhancements
    • Triage/Bugs Filed
      • 312285 all tests in jpa jpaadvancedproperties model failed on GlassFish V3 only in trunk
      • 312303 Newly added test - jpa.jpql.JUnitJPQLComplexTestSuite.testComplexLike failed on Derby
  • This week
    • Informix JPA hang investigation
    • Enable SDO server tests to run nightly on all app servers
    • EL 2.1 test dev - finish Advanced JPA Config test spec
    • Downcast test suite enabled to run on all application servers
    • Review Fetch groups (if test code checked in).
    • EclipseLink 2.1 Release testing kick-off
      • start tracking closedown of release
    • Fix Bugs

Build

  • Milestone Releases
    • 2.0.2 Patchset available
    • M7 Helios contribution available
  • "target platform" work for Helios (bug 306188)
    • Completed
  • Document EclipseLink's "Infrastructure"
  • Helios build integration (293034)
  • Modify Ant build to require bnd, or use dev manifests if flag provided.
    • complete. May be conflicting logic issues with weaving/equinox. investigating.
  • Working on way to detect jarnames of a dependency.
    • need to insure issues like occurred with 2.0.2 don't recurr
    • also need to check for bnd.
    • many other uses.
  • 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).
  • 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

April 30 - May 6, 2010:

2.1.0

  • Advanced JPA config
    • Dynamic persistence
  • Advanced JPA Querying
    • Fetch groups still in progress
  • OSGI
    • Gemini integration work
    • Initial set of updates checked in
  • Bug Fixes

DBWS

DBWS Development

2.1.0

  • 307897 - Alternative solution to using ASM to generate JAX-WS provider. Resolved (works with dependency on tools.jar, no CQ required)
  • 290156 Validate SOAP message elements. Moved to target=Future as basic SOAP element validation is already in plase.
  • 310289 Provide DBWSBuilder support for Eclipse WTP Dynamic Web Project structure. Checked in
  • Scoping out potential EclipseLink feature work
    • Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)

SDO / MOXy

2.0.3

  • 309869 Time Zone does not marshal correctly for DST - resolved

2.1.0

  • Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
    • MOXy Mapping Extensions - Phase 6 complete
    • Phase 7
      • Inverse reference mapping - complete
      • Fragment mapping
      • Transformation mapping
  • MOXY Dynamic Persistence Design
    • Bootstrapping from Schema
      • Phase 10 complete
        • Exception - Enum support (requiring core Dynamic Persistence change)
    • Dynamic MOXy code moved into a new project - org.eclipse.persistence.moxy.dynamic
      • Eclipse IDE build changes needed if you are using MOXy projects
  • JAXB2.2 Compliance complete
    • EclipseLink build switched over to use JAXB2.2 jars from Orbit
  • SDO Server testing
    • Plan to run automated SDO server tests against JBoss, WAS, WLS app servers.

Dynamic Persistence

Dynamic Persistence

EclipseLink Incubator

EclipseLink/Development/Incubation

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

Bugs By Target and Priority

Resolved Bugs

Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

Back to the top