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 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

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

QA

June 11 - 17, 2010:

  • Nightly Results
    • 2.1 (rc4.2 v20100614-r7608) - all good
    • trunk (2.2) - Tests for last night's build did not run - the build completed too late; WDF tests failed (for one week) - SAP investigating
    • 1.1.4 - 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
    • EclipseLink 2.1 - Testing Completed
      • 316531 JPA/Websphere - fixed in 2.2 and will be backported to 2.1.1. - worked with Dev to resolve
      • Functional testing (automated nightly) triage: 100%
      • DB Certification testing (automated nightly) triage: 100% - JPA OOC PostGreSQL - 100%
      • Functional Manual testing: JPA Configs - 95% (Glassfish remains); WebLogic Integration - 100%; Cache Co-ord (WLS 10.3.3) - 100%
      • Certification Manual testing: JPA/Sybase - 100%; JPA/Informix - 100%; JPA/Timesten - in progress; JPA/SQLServer - 100%; Linux - 100% ; Windows - 100%
    • Glassfish v.3 test failures on Windows - fixed our config scripts; confirmed config with Mitesh
    • osgi/Gemini - investigation ongoing
    • Fixed Bugs
      • ...
    • Test Dev 2.2/2.1.1 - EL 2.1 Advanced Query:
      • Downcast test dev - 15%
      • FUNC test dev - 95% - need review; added stored function test, tests specific to MySQL, added tests for orderBy, groupBy
      • Fetch Group test dev - 30% - no change; tests migrated to run on servers (half failed, so not checked in yet)
    • test fwk enhancements
      • Enabled the Triage Assistant to deal with the java.lang.NullPointerException case
    • Triage/Bugs Filed
      • ...
  • This week
    • Continue with remaining Advanced Query test dev on 2.2/2.1.1 stream
    • Gemini/osgi investigation
    • Fix Bugs:

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: fixed EclipseLink issues in joint Helios bug 316720.

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
    • Investigating how to access ServletContext on Glassfish in platform independent way
  • 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

  • Update 2.1 release notes to reflect new content from a user's perspective
  • Investigating intermittent MOXy/SDO test failures on nightly builds.
  • 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
  • OSGi testing
    • Investigating whether core bundle can be broken apart to solely provide support for JAXB bundle
  • 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

Retrieved from "https://wiki.eclipse.org/index.php?title=EclipseLink/Development/DevMeetings&oldid=208584"

Back to the top