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

< EclipseLink‎ | Development
Revision as of 10:53, 8 July 2010 by Peter.krogh.oracle.com (Talk | contribs) (Release Planning)



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 Jun 10, 2010

11 am EST, Thurs Jun 10, 2010


Ad Hoc

  • Intermittent failures on build machine: what good are the reports if we can't trust them?
    • Different test failure each time.
  • EclipseLink Summit Wrap-up
    • Comment on notes from Thursday sessions to ensure we captured all the important points (dev mailing list)
    • Open issues will be added to this agenda
      • This Week - Looking at some of the build issues.
    • Process topic of contribution log - Please make sure all new code in 2.1 has proper header and dates
      • a sweep of 2.1 was done last week.


Release Planning

  • 2.1.1
  • 1.2.1
    • requests to shut this down...
  • 2.0.3
    • June/July

QA

June 18 - 24, 2010:

  • Nightly Results
    • trunk - no issues
    • 2.1.1 - no recent checkins, but nightly testing enabled
    • 1.1.4 - no issues; resolved - WAS and Glassfish 2 failures - most likely test infra issue (moved servers)
    • 2.0.3 - no new builds
    • 1.2.1 - frozen: no issues (last build May 6)
  • Last week
    • osgi/Gemini - investigation ongoing
    • Fixed Bugs
      • 317189 test implementation for Advanced Query --- FUNCTION support to extended JPQL
    • Test Dev 2.2/2.1.1 - EL 2.1 Advanced Query:
      • Downcast test dev - in progress - 90% - ETA: June 5
      • FUNC test dev - 100% - reviewed and checked in; will backport to 2.1.1
      • Fetch Group test dev - 35% - tests migrated to run on servers (fix some failures on server by adding separate persistence.xml for server testing)
    • test fwk enhancements
      • Add WAS ND JPA testing in nightly run
      • Started to work on a way to automatically kill overdue processes and send alerts in order to solve hanging issues
      • Enhanced function certifyDBNonOracle() to support finer granularity - can run just core, JPA, etc... instead of all tests
    • Triage/Bugs Filed
      • 317603 CREATE FUNCTION StoredFunction_In (...) RETURN ... doesn't work with MySQL 5.1.39
  • This week
    • Advanced JPA Config test dev
    • Fetch Groups test dev.
    • Gemini/osgi investigation
    • Continue - way to automatically to kill overdue processes and send alerts in order to solve hangup issues

Build

  • Helios Released
    • EclipseLink 2.1.0.v20100614-r7608 in Helios repo
  • Milestone Releases
    • none
  • Working on way to detect jarnames of a dependency. Part of 312437.
    • ant task debugged, reviewed by Mike Norman, and merged.
    • need to hook into build for bnd detection.
    • in future can be used to detect jars to use for latest Orbit drops, and other dependency checks.
  • EclipseLink Summit Items to review:
    • Move to PDE build? (drop ant)
      • Advantages: get many features now have to 'hack'
      • Disadvantages: tied to someone else's process. May not work with our versioning. Web distributions, etc.
      • If we decide to drop ant support will need to plan phase-out, and investigate PDE capabilities further.
    • Rename build.xml and build.properties (260428)
      • what to rename to? antbuild? eclipselink? suggestions?
  • Review process for build bugs?
    • Future direction of build?
      • Creating Wiki page to capture open issues and help plan improvements (It will also capture bugs below)
        • Review and vote? on: 260428 273911 279176 295071 298286 298790 299060 301698 (303006 close?) 303621 303630 305386 308919 309853
        • Once created can revisit review process.

Fixed Bugs:

JPA

June 10 2010:

2.1.0

  • Advanced JPA config
    • Dynamic persistence
  • Advanced JPA Querying
    • Fetch groups still in progress
  • OSGI
    • Initial Gemini Integration done
      • No Weaving
  • Bug Fixes

DBWS

DBWS Development

2.2

  • Target DBWS support for Glassfish, JBoss, Websphere
    • Determining how to create a fragment/bundle for DBWS that can installed as an update into Glassfish.
    • Assuming user will be able to select this fragment as an optional update
  • Sparse Merge Support
    • EclipseLink2.2 goals reviewed with PM
    • Investigating how to create a dynamic entity which contains a partial FetchGroup
    • Reviewed isSet() behaviour used in Dynamic Persistence
    • Building on top of Fetch Group feature introduced in EclipseLink2.1 - identifying usecases and setting up initial Proof of Concept

SDO / MOXy

2.1.1

  • MOXy externalized metadata
    • Couple of issues identified that will need backporting to 2.1.1
    • Working on accompanying examples for 2.1 release

2.2.0

  • MOXy External Metadata support
    • Provide alternative annotation support for MOXy advanced mappings
    • Identify entries in deployment.xml that are currently not represented in external XML file.
  • MOXY Dynamic Persistence
    • Provide ability to bootstrap from external MOXy XML file
  • SDO Server testing
    • Running automated SDO server tests against JBoss, WAS, WLS app servers.
    • Test SDO against Glassfish to determine the current level of support
  • Feature work: Platform integration
    • 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.

EclipseLink Incubator

EclipseLink/Development/Incubation

Documentation

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

Back to the top