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,ATOM News Feed,HTML

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 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 starting next week
  • Process topic of contribution log - Please make sure all new code in 2.1 has proper header and dates

Release Planning

• 2.1 Helios
  • http://www.eclipse.org/projects/project-plan.php?projectid=rt.eclipselink
  • Final RC build goes to Eclipse repository Monday June 7. After this, only showstoppers can be included.
  • Need to finish triaging bugs targeted for 2.1 that will not be completed - need to be better at bug ramp down next time
  • Ensure all critical release process tasks have bugs created and assigned (wiki, downloads, announcements, examples)

• 1.2.1
  • requests to shut this down...

• 2.0.3
  • June?

• Future Release Planning starting
  • 2.2 - 6-8 months after Helios?
  • 2.3/3.0 - Indigo in June 2011

QA

May 14 - May 20, 2010:

• Nightly Results
  • 2.1 - JPA H2 issues - intermittent? (monitor)
  • 1.1.4 - no recent builds : no issues
  • 2.0.3 - no issues
  • 1.2.1 - frozen: no issues (last build May 6)
• Last week
  • EclipseLink 1.2.1
    • All DB test results triaged
    • JPA manual tests for 1.2 (e.g. non-JTA/JTA, Weaving options, etc) for WLS, WAS, JBoss - 100%
  • EclipseLink 2.1
    • Functional testing (automated nightly) triage: 100%
    • DB Certification testing (automated nightly) triage: 100%
    • Functional Manual testing: JPA Configs - 20%; WebLogic Integration - 0%; Cache Co-ord - 0%
    • Certification Manual testing: JPA/Sybase - 0%; JPA/SQLServer - 0%; Linux - 100% ; Windows - 30%
  • Fixed Bugs
    • 312689 Need to give correct schema name for namespace in seesions.xml for JPA testing
    • 312285 all tests in jpa jpaadvancedproperties model failed on GlassFish V3 only in trunk
    • 308880 Need to generalize SDO tests for WLS to run with other application servers
    • 311782 Need to enable the SDO tests for server to run with WLS, WAS and JBoss
  • Enable SDO server tests to run nightly on all app servers - 100% - WLS, WAS, JBoss running nightly
  • Informix JPA hang - investigated, there is workaround to run all tests but solution not found yet.
  • Fixed test failures in OSGi example and SRG
  • EL 2.1 Advanced Query
    • QueryCastTestSuite (Downcast) now running inside container
    • FUNC tests running inside container
  • EL 2.1 Advanced JPA Config - test plan - 100% - in review process
  • test fwk enhancements
    • some minor changes, switched to JDK1.6.0_20
    • Removed old SDO server tests
  • Triage/Bugs Filed
    • 296376 (Reopen) testSetRollbackOnly() in advanced and fieldaccess advanced models failed on GlassFish V2 against Oracle 11.1.0.7
    • 296380 (Reopen) testSequenceObjectDefinition() in fieldaccess/advanced model failed on GlassFish V2 against Oracle 11.1.0.7
    • 296381 (Reopen) all four tests in JPA DelimitedPUTestSuite failed on GlassFish V2 against Oracle 11.1.0.7
    • 312303 Newly added test - jpa.jpql.JUnitJPQLComplexTestSuite.testComplexLike failed on Derby
• This week
  • EclipseLink 2.1 Testing
  • SpatialJPQLTestSuite for FUNC support of Advanced Query running on all application servers
  • Fetch Groups test review and test implementation (migration to run on app servers)
  • EclipseLink 2.1 Release Testing
  • Documentation - update test execution instructions on Wiki
  • Fix Bugs:
    • 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

Build

• Milestone Releases
• Document EclipseLink's "Infrastructure"
  • Wiki page created. Updates needed for new process.
    • Page can be found at http://wiki.eclipse.org/EclipseLink/Infrastructure
• 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

May 28 - June 2 2010:

2.1.0

• Advanced JPA config
  • Dynamic persistence
• Advanced JPA Querying
  • Fetch groups still in progress
• OSGI
  • Initial Gemini Integration done
  • Investigation into weaving for Gemini on Equinox
• 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

SDO / MOXy

2.1.1

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

• EclipseLink/Development/Incubator/Extensions
  • MaxDB work in progress
• Time to create separate sub-project for incubator
  • Increase community of committers
  • Try out GIT & eGit/jGit tooling in incubator?

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