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"

(SDO / MOXy)
(Build)
Line 61: Line 61:
 
== Build ==
 
== Build ==
 
* Milestone Releases
 
* Milestone Releases
** None
+
** M6 EclipseLink
** Upcoming: 2.1.0 M6 next Wednesday
+
** M6 Helios contribution (nightly build)
* Test component build cleanup (Holding)
+
*** Due to an uncaught bug found by the Helios build system.
** Restructure to allow testing to *not* rebuild product jars (293032)
+
*** We need to modify our milestone strategy. Milestones should be promoted *after* the Helios contribution is made.
*** Will use "static targets" as discussed in meeting last week (297217).
+
* "target platform" work for Helios (bug 306188)
*** Tests will not compile when run target called.  
+
** RT is requesting we simplify how we are included in RT - siingle SDK
**** merged partial work to update standards.
+
*** the one feature can and should simply include our other already existing features.
**** migration work for test projects, currently priority 2
+
* As of M6 EclipseLink is no longer shipped with the Java EE Package
** Need shippable testing artifacts (R2).
+
** As a team we need to decide:
* Helios build integration (293034)
+
*** What we should offer regarding IDE tooling that helps the developer use EclipseLink
 +
*** If we should help another team provide it (Dali ?)
 +
* Helios build integration (293034) (Blocked until Post M6)
 
** Need to do p2 consolidation work to manage multiple versions in a single update location.
 
** Need to do p2 consolidation work to manage multiple versions in a single update location.
 
*** investigation composite repositories
 
*** investigation composite repositories
 
**** Have working prototype.  
 
**** Have working prototype.  
 
**** Working on creating a Composite of all our releases - (completed locally).
 
**** Working on creating a Composite of all our releases - (completed locally).
***** Cannot generate on Download machine due to bug 303802.
+
***** Cannot generate on Download machine due to bug 303802 fix will be available in M6 helios release.
 
**** Still need to finalize automation.
 
**** Still need to finalize automation.
 
***** Automation for Composite work still pending. Looks like a separate script will be necessary.
 
***** Automation for Composite work still pending. Looks like a separate script will be necessary.
Line 82: Line 84:
 
***** Awaiting confirmation of a bugfix before commit (Blocked by bug 303802).
 
***** Awaiting confirmation of a bugfix before commit (Blocked by bug 303802).
 
***** Still need to finalize automation (Blocked by bug 303802).
 
***** Still need to finalize automation (Blocked by bug 303802).
* jpa.test10 Suite - Holding
+
* 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
 
** 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.
 
*** All tests now compiling with trunk, 83% success rate on Test run.

Revision as of 06:10, 18 March 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 Mar 4, 2010

11 am EST, Thurs Mar 4, 2009

Ad Hoc

Release Planning

QA

Mar 05 - 11, 2010:

  • Last week
    • Monitor and triaged nightly tests:
      • 1.1.4 - good
      • 2.0.2 - good
      • 1.2.0 - good
      • trunk - some new failures with Oracle extension tests, investigating by Eric, Edwin and Andrei. Will be fixed soon.
      • Filed 2 bugs from last weeks nightly results - 305040, 30538
    • Fixed Bugs - 304862, 301837
    • JPA 2.0 TCK enable nightly - in progress
    • Reviewed current test bug backlog and targeted bugs to be fixed for 2.1
    • EL 2.1 Advanced Query - learning/planning phase - in progress
    • Triaged JPA tests failure on JBOSS Enterprise Application Platform 5.0.0 GA
    • JPA/WebLogic with Derby - issues with creating datasources - filed bug 304873
  • This week
    • EL 2.1
      • Advanced querying - review current tests
      • JAXB 2.2
    • JPA 2.0 TCK - nightly
    • Fix Bugs

Build

  • Milestone Releases
    • M6 EclipseLink
    • M6 Helios contribution (nightly build)
      • Due to an uncaught bug found by the Helios build system.
      • We need to modify our milestone strategy. Milestones should be promoted *after* the Helios contribution is made.
  • "target platform" work for Helios (bug 306188)
    • RT is requesting we simplify how we are included in RT - siingle SDK
      • the one feature can and should simply include our other already existing features.
  • As of M6 EclipseLink is no longer shipped with the Java EE Package
    • As a team we need to decide:
      • What we should offer regarding IDE tooling that helps the developer use EclipseLink
      • If we should help another team provide it (Dali ?)
  • Helios build integration (293034) (Blocked until Post M6)
    • Need to do p2 consolidation work to manage multiple versions in a single update location.
      • investigation composite repositories
        • Have working prototype.
        • Working on creating a Composite of all our releases - (completed locally).
          • Cannot generate on Download machine due to bug 303802 fix will be available in M6 helios release.
        • Still need to finalize automation.
          • Automation for Composite work still pending. Looks like a separate script will be necessary.
      • Migration from p2.metadata.generator to p2.publisher (Blocked by bug 303802).
        • Prototype complete.
          • Awaiting confirmation of a bugfix before commit (Blocked by bug 303802).
          • Still need to finalize automation (Blocked by bug 303802).
  • 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

Feb 26 - Mar 4

2.1.0

  • OSGi
    • investigation on hold. Gemini.
  • Bugs with Votes
    • '.' notation querying bug fix broke compliance tests. It is being closed as WONTFIX.
    • Bug related to FindBugs and primitive literals started

DBWS

DBWS Development

2.0.2

  • 303331 Complex PL/SQL record parameter as INOUT argument to Stored Procedure not returning OUT information: Resolved.


2.1.0

  • Scoping out potential EclipseLink feature work
    • Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)

SDO / MOXy

2.0.2

  • 306054 JAXB Externalized Metadata: factory class and method missing from xml-type declaration in XSD

Closed this week:-

  • 301062 MOXy - JAXB: Issues with multiple XmlElementDecl with same QName and different scope
  • 305572 xsi:type on composite mappings with no ref descriptor not working in default namespace
  • 306027 Namespace prefix for xsi:type value may not resolve when namespace declaration on current element using StAX
  • 306194 JAXB Extension - Generate appropriate schema types for java.sql.* classes
  • 305999 JAXB Externalized Metadata: Schema gen incorrect for non-generic list
  • 306008 XmlCustomizer class is loaded using the wrong classloader

2.1.0

  • Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
  • MOXY Dynamic Persistence Design
  • JAXB2.2 Compliance
    • JAXB2.2 CQs approved (API, RI, XJC).
    • Also need to submit JAXB2.1.12 jars to Orbit (CQs previously approved for Helios)

Dynamic Persistence

Dynamic Persistence

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

Open Bugs

Date 1.1.4 1.2.1 2.0 2.0.1 2.0.2 2.1 Future/1.1.x Untargetted
February 11, 2010 1 1 x 3 x 80 523 142
January 14, 2010 1 2 x 42 x 52 496 142
December 7, 2009 4 5 3 25 x 30 495 149
November 12, 2009 2 2 186 6 x x 357 131
November 5, 2009 1 1 189 3 x x 354 131
October 29, 2009 1 1 194 x x x 345 125
October 22, 2009 0 0 203 x x x 362 131


Bugs By Target and Priority

Resolved Bugs

Date 1.1.x 1.2.x 2.0 2.0.x 2.1 Invalid Duplicate Submitted Patch
February 11, 2010 1 3 x 26 17 8 9 3
January 13, 2010 0 1 1 10 4 3 1 0
December 7, 2009 2 1 71 0 3 12 18 0
November 11, 2009 0 0 15 x x 6 2 0
November 4, 2009 0 1 20 x x 5 1 0
October 28, 2009 0 1 26 x x 4 2 2
October 21, 2009 0 2 20 x x 2 1 1

Resolved Bugs

New Bugs

Date 1.1.4 1.2.1 2.0 2.0.1 2.0.2 2.1 Future Enhancement Already resolved
February 8, 2010 1 1 x 15 2 18 31 7 32
January 13, 2010 2 0 x 10 x 11 28 9 20
December 7, 2009 1 3 35 8 x 3 37 10 56
November 11, 2009 0 0 8 3 x x 3 2 2
November 4, 2009 1 2 17 3 x x 4 0 0
October 28, 2009 0 1 10 x x x 8 0 6
October 21, 2009 0 0 9 x x x 0 0 4


Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

Back to the top