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

Difference between revisions of "EclipseLink/Development/DevMeetings"

(DBWS)
m (SDO / MOXy)
Line 135: Line 135:
 
== SDO / MOXy  ==
 
== SDO / MOXy  ==
 
2.1.1
 
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.
 
* Investigating intermittent MOXy/SDO test failures on nightly builds.
 
* Some issues highlighted with MOXy externalized metadata - fixing in trunk, plan to backport to 2.1.1.
 
* Some issues highlighted with MOXy externalized metadata - fixing in trunk, plan to backport to 2.1.1.

Revision as of 14:41, 16 June 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.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
  • Future Release Planning starting
    • 2.2 - 6-8 months after Helios?
    • 2.3/3.0 - Indigo in June 2011

QA

June 4 - 10, 2010:

  • Nightly Results
    • 2.1 (rc4.1) - functional tests good, db cert - Postgre issue (see below)
    • trunk - 2 new failures on JBoss - investigating
    • 1.1.4 - no issues
    • 2.0.3 - no issues
    • 1.2.1 - frozen: no issues (last build May 6)
  • Last week
    • EclipseLink 2.1
      • Functional testing (automated nightly) triage: 100%
      • DB Certification testing (automated nightly) triage: 100% - JPA OOC PostGreSQL - Native Query 4 tests - investigating most likely test case issue
      • 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 - in progress; JPA/Timesten - in progress; JPA/SQLServer - 100%; Linux - 100% ; Windows - 100%
    • Fixed Bugs
      • 310329 ValidationException is thrown when deploy jpa 2.0 cacheable test model on Server
      • 316365 JPA testing on Glassfish v3 should use the same bundle jars to overwrite the existing bundle jars in Glassfish install
      • 315119 change several test framework classes to eliminate dynamic test case names
      • 293425 ANT target <test-non-lrg> under trunk/foundation/eclipselink.core.test hangs with JRockit 1.6
      • 312302 Need to add re-deploy aspect to SDO server testing
    • EL 2.1 Advanced Query
      • Downcast test dev - 15%
      • FUNC test dev - 50% - added stored function test
      • Fetch Group test dev - 30% - tests migrated to run on servers (half failed, so not checked in yet)
    • EL 2.1 Advanced JPA Config - no progress
    • test fwk enhancements
      • Testing infra for EclipseLink 2.1 branch created
    • Triage/Bugs Filed
      • 315119 change several test framework classes to eliminate dynamic test case names
      • 315097 jpa.advanced.EntityManagerJUnitTestSuite.testCreateEntityManagerFactory2 on WLS only failed on Windows
      • 315242 eight tests in jpa.xml.merge.inherited.EntityMappingsMergeInheritedJUnitTestCase failed on Servers only with static weaving
  • This week
    • EclipseLink 2.1 Release Testing
    • Continue with remaining Advanced Query test dev on 2.1.1 stream
    • Gemini/osgi investigation
    • Setup another DB certification machine.
    • Fix Bugs:

Build

  • Milestone Releases
    • 2.1.0 RC4 - Completed (removed from download page)
    • 2.1.0 RC4.1 - Replaced RC4 for Helios contrib, and on download site.
  • 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.
  • Review process for build bugs?
    • Future direction of build?
    • Review and vote? on: 260428 273911 279176 295071 298286 298790 299060 301698 (303006 close?) 303621 303630 305386 308919 309853

Fixed Bugs: closed many that had been left open inadvertently.

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.1.1/2.2

  • Sparse Merge Support
    • First phase (changes to Dynamic Persistence) ready for review
    • Building on top of Fetch Group feature introduced in EclipseLink2.1 - identifying usecases and setting up initial Proof of Concept
  • Target DBWS support for Glassfish, JBoss

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.
  • Some issues highlighted with MOXy externalized metadata - fixing in trunk, plan to backport to 2.1.1.
  • 315478 Strange behaviour converting String to Dates if date is before Gregorian Switch
  • 316014 Tweak MOXy's XMLStreamWriterRecord to work with Jettison's JSON/StAX support
  • 313545 Eclipselink is losing some data for certain types of data structures when unmarshalling xml to java objects

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

  • 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