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:41, 29 October 2009 by Peter.krogh.oracle.com (Talk | contribs) (→‎Milestones)


Dial In Info:

  • please contact 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 Oct 22, 2009

Meeting format:

  • Milestones
  • Work Allocation
  • Completed
  • @Risk

11 am EST, Thurs Oct 22, 2009

  • remove .settings/org.eclipse.jdt.core.prefs from SVN version control

Ad Hoc

Milestones

  • Google calendar above.
  • 1.1.3 Patch Set - Released Oct 9/09
  • 1.2.0 Release - Pending
  • 2.0.0 Release - rescheduled for Dec ../09?
  • 2.0.0 Weekly Milestones until release
    • M10 - released Oct 19/09
    • M11 - scheduled Oct 26/09
    • M12 - scheduled Nov 2/09
    • M13 - scheduled Nov 9/09
    • RC1 - scheduled Nov 16/09
    • RC2 - scheduled Nov 23/09
      • Branch? at this point
    • GA - scheduledDec 10th


  • Helios - Annual release - June 24/2010
    • M1 - August 21/09: Included EclipseLink 1.1.3 M1
    • M2 - October 2/09: Included EclipseLink 1.1.3 RC1
    • M3+1 - November 9/09: targeting inclusion of EclipseLink 1.1.3 Release
    • M3 - November 13/09: Available
    • M4+1 - December 14/09: targeting inclusion of EclipseLink 2.0.0 GA?
    • M4 - December 18/09: Available
  • Galileo SR2 - February 26th/2010
    • RC1+0 Jan 18/10: EclipseLink 1.1.x (latest Milestone or Release)


QA

  • Work allocation this week
  • Completed this week

Build

  • Milestone Releases
    • 2.0.0 M10
    • 1.2.0 Release (Holding)
  • Move Oracle extension submission process to svn (293030)
    • Complete.
  • Need to add missing artifacts to Maven (293039)
    • Had been determining requirements.
    • Starting development work
  • Maven submissions need to include dependecy info for artifacts (279177)
    • Currently investigating requirements
  • Test component build cleanup
    • Complete "Build rework" on these components (260295).
    • Restructure to allow testing to *not* rebuild product jars (293032)
    • Need shippable testing artifacts (R2).
  • Helios build integration (293034)
    • Local transaction to:
      • update "features" for Helios
      • add jar signing, and packing
    • Cannot merge until javax.persistence_2.0_preview jar becomes javax.persistence_2.0.0*.jar (targetted for Nov 2)

Fixed Bugs: 293030, 236677

JPA

Completed

  • The 'final' API updates are checked in.
    • Jar still called 2.0_preview.
  • closing in on 0 failures with JavaSE tck results

Work allocation

  • JPA 2.0
    • Triage of bugs
      • Review submitted patches

DBWS

  • Completed
  • Work allocation
    • move to core Dynamic Persistence
  • DBWS

SDO / MOXy

  • Work Allocation
  • Completed
  • SDO
    • EclipseLink1.1.1 fully passes the SDO2.1.1 TCK on JDK1.5 and JDK6.
  • MOXy
    • EclipseLink2.0: targetting JAXB 2.1.x compliancy.

287296 SDO: Need to be able to compile against SDO 1.0 Jar 287690 JAXB - exception is thrown when it shouldn't be (xmlvalue annotation on enum) 287855 Exception unmarshalling from XmlStreamReader with class to unmarshal to specified 288131 Unmarshalfrom XMLStreamReader stress test causes StackOverFlow Error 288297 NPE unmarshalling from StreamReader if startDocument isn't triggered 286316 SDOProperty should set schema type of BinaryDataMapping to base64Binary 286872 AnnotationsProcessor should use new "isRequired" API


EclipseLink Incubator

EclipseLink/Development/Incubation

Bug Status

Bug reports

Foundation and JPA

Open Bugs

Date 1.1.4 1.2.1 2.0 Future/1.1.x Untargetted
October 22, 2009 0 0 203 362 131


Bugs By Target and Priority

Resolved Bugs

Date 1.1.x 1.2.x 2.0 Invalid Duplicate Submitted Patch
October 21, 2009 0 2 20 2 1 1

Resolved Bugs

New Bugs

Date 1.1.4 1.2.1 2.0 Future Enhancement Already resolved
October 21, 2009 0 0 9 0 0 4


Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

General Issues

  • Running JPA in JavaSE mode on trunk
    • Issues due to jar signing and split javax.persistence package
    • If you run in Java SE with the javax.persistence 1.0.0 jar shipped with EclipseLink and eclipselink.jar you will get security exceptions on our trunk stream (but not our released streams)
    • We solve this in our testing with an unsigned version of the javax.persistence jar. We may have to consider a similar strategy for our "installer-zip" distribution.
  • SPI defaulting
    • We provide a number of service advertisements in META-INF/services of eclipselink.jar
    • It is possible that installing eclipselink.jar to make use of one service (e.g. JPA) will transparently change the provider of another service (e.g. JAXB) to use EclipseLink if the user has not explicitly specified their service providers.
  • Wiki site update
    • Ensure that wiki site reflect state of feature
  • Location of Docs moving forward
    • where to put 2.0 documentation.
    • breaking down features into smaller pages.
    • potential clone of wiki.


Upcoming Issues

The following items require discussion but are not yet at the stage where a solution can be proposed.

Minutes from Past Meetings

References

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

Back to the top