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"

(QA)
(QA)
Line 49: Line 49:
 
*** 290069 - testOrderCustomerMapping within jpa.xml.merge.relationships.EntityMappingsMergeRelationshipsJUnitTestCase failed on JBoss   
 
*** 290069 - testOrderCustomerMapping within jpa.xml.merge.relationships.EntityMappingsMergeRelationshipsJUnitTestCase failed on JBoss   
 
*** 274584 - testUpdateUsingTempStorageWithParameter and testUpdateUsingTempStorage failed on SQL Server 2k5   
 
*** 274584 - testUpdateUsingTempStorageWithParameter and testUpdateUsingTempStorage failed on SQL Server 2k5   
 +
*** 305865 - jpa.fieldaccess.advanced.AdvancedJPAJunitTest.testPessimisticLockingNamedQuery failed on Derby
 +
*** 305330 - EclipseLink JPA tests failed On JBOSS EAP 5.0.0 GA JNDI lookup failure of EJB Proxy Factory 
 +
*** 305331 - Unsigned eclipselink.jar doesn't work with signed ejb3-persistence.jar for JPA testing on JBOSS EAP 5.0.0 GA 
 
** JPA 2.0 TCK enable nightly - completed
 
** JPA 2.0 TCK enable nightly - completed
 
** EL 2.1 Advanced Query - FUNC support test spec 90%; Downcast - reviewing dev documentation
 
** EL 2.1 Advanced Query - FUNC support test spec 90%; Downcast - reviewing dev documentation

Revision as of 11:00, 25 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 19 - 25, 2010:

  • Nightly Results
    • 1.1.4 - JPA/Glassfish 2.0 jpql test failires
    • 2.0.2 - clean
    • 1.2.0 - no recent builds
    • trunk - JPA/J2SE no weave 5 tests failed - investigating
  • Last week
    • Fixed Bugs
      • 296279 - jpql.JUnitJPQLComplexTestSuite.complexConstructorCaseTest failed with Derby
      • 290069 - testOrderCustomerMapping within jpa.xml.merge.relationships.EntityMappingsMergeRelationshipsJUnitTestCase failed on JBoss
      • 274584 - testUpdateUsingTempStorageWithParameter and testUpdateUsingTempStorage failed on SQL Server 2k5
      • 305865 - jpa.fieldaccess.advanced.AdvancedJPAJunitTest.testPessimisticLockingNamedQuery failed on Derby
      • 305330 - EclipseLink JPA tests failed On JBOSS EAP 5.0.0 GA JNDI lookup failure of EJB Proxy Factory
      • 305331 - Unsigned eclipselink.jar doesn't work with signed ejb3-persistence.jar for JPA testing on JBOSS EAP 5.0.0 GA
    • JPA 2.0 TCK enable nightly - completed
    • EL 2.1 Advanced Query - FUNC support test spec 90%; Downcast - reviewing dev documentation
    • EL 2.1 Advanced JPA Config - reviewing dev documentation
    • JAXB 2.2 TCK - automation work completed
    • Changed test scripts to fix issues with running JPA/JBoss EAP (JBoss Community has always run)
    • Triage - 7 bugs filed
  • This week
    • Continue with EL 2.1 test dev work - Advanced querying, Advanced JPA config
    • Enable SDO/Websphere
    • 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

  • No remaining bugs

2.1.0

  • 290156 Validate SOAP message elements
  • 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

  • All 2.0.2 bugs resolved

Closed this week:-

  • 305401 Support required for SDO Serialization/Deserialization using local helper contexts
  • 306436 JAXB Externalized Metadata: Need to support XmlDirectMapping config via metadata file
  • 306542 JAXB Externalized Metadata JUnit: 1 failing XmlDirectMapping test on IBM VM
  • 306828 JAXB Externalized Metadata: Need to support XmlCompositeObjectMapping config via metadata file

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
    • JAXB 2.1.12, 2.2 API, Impl jars submitted to Orbit

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

Bugs By Target and Priority

Resolved Bugs

Created Bugs


EclipseLink/Development/DevMeetings/ArchiveBugReports

Back to the top