Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/DevMeetings"
< EclipseLink | Development
(→QA) |
(→Ad Hoc) |
||
| Line 29: | Line 29: | ||
=== Ad Hoc === | === Ad Hoc === | ||
| + | Intermittent failures on build machine: what good are the reports if we can't trust them? | ||
| + | |||
EclipseLink Summit: http://wiki.eclipse.org/EclipseLink/Development/Summit | EclipseLink Summit: http://wiki.eclipse.org/EclipseLink/Development/Summit | ||
Revision as of 09:01, 22 April 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,
ATOM News Feed,
HTML
Agenda Apr 8, 2010
Ad Hoc
Intermittent failures on build machine: what good are the reports if we can't trust them?
EclipseLink Summit: http://wiki.eclipse.org/EclipseLink/Development/Summit
Release Planning
- 2.0.2: Proposed date: April 21st\
- Stream is now frozen. Showstoppers approved by Doug/Peter only.
- 2.1 Helios
QA
April 9 - April 15, 2010:
- Nightly Results
- 1.1.4 - no recent builds
- 2.0.2 - build last night was clean
- 1.2.1 - no recent builds
- trunk - Spring tests 2 failures (investigated) ; WDF tests failed (fix checked in)
- Last week
- Fixed Bugs
- none
- SDO server tests generalization to run on all app servers - 70%
- WDF tests / JBoss automated, not running nightly - will run nightly next week after current failures resolved
- WDF tests on WLS and Glassfish (ran manually) - fwk changes required
- EL 2.1 Advanced Query
- Downcast - documents reviewed, reviewed example
- EL 2.1 Advanced JPA Config - test plan in progress - ETA: April 22
- Triage/Bugs Filed
- 309307 - 14 XML_SCHEMA tests from JAXB TCK failed with JDK1.6.0_17 and latest
- 308880 - Need to generalize SDO tests for WLS to run with other application servers
- 309037 (WDF) - Should not load lower lever test.properties in the build.xml under trunk directory
- Fixed Bugs
- This week
- SDO server tests generalization to run on all app servers
- WDF - work with Adrian in getting tests running on other app servers
- Continue with EL 2.1 test dev work - test plan for Advanced JPA config
- Cache Co-ord testing on Windows
- Informix DB
- Fix Bugs
- 287222 - All new added JPA 2.0 tests need to be modified to run on JPA 2.0 servers
- 293614 - JPA 2.0 Cacheable Test Suite need to be enabled for JPA 2.0 servers
Build
- Milestone Releases
- 2.0.2 Release Pending
- M7 Helios due May 3
- Note: Milestones will be promoted *after* the Helios contribution is made and tested.
- "target platform" work for Helios (bug 306188)
- RT is requesting we simplify how we are included in RT - single SDK featue
- the one feature can and should simply include our other already existing features.
- I have created and put new feature in local P2 repos. Testing thus far shows it works as expected.
- Need to determine overall P2 repos plan before implementing fix.
- RT is requesting we simplify how we are included in RT - single SDK featue
- Document EclipseLink's "Infrastructure"
- Wiki page in progress.
- Helios build integration (293034) (May be perminently blocked due to limitation with categories)
- Need to do p2 consolidation work to manage multiple versions in a single update location.
- investigation composite repositories
- Have working prototype.
- Migration from p2.metadata.generator to p2.publisher (Completed, but not merged).
- Still need to finalize automation (Blocked by bug 303802).
- investigation composite repositories
- Need to do p2 consolidation work to manage multiple versions in a single update location.
- 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).
- Restructure to allow testing to *not* rebuild product jars (293032)
- 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%
- 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
Fixed Bugs:
JPA
April 2 - April 8, 2010:
2.0.2
- no bugs
2.0.x
- two bug fixes waiting on reopen of stream
- Exteranious logging
- Blob/Clob Length
- two bug fixes waiting on reopen of stream
2.1.0
- Advanced JPA config
- Dynamic persistence
- Advanced JPA Querying
- Downcast queries implementation
- Fetch Group
- Bug Fixes
- Cache evict
- Native Case sensitivity
DBWS
2.0.2
- No remaining bugs
- Providing release note for issue when deploying DBWS war file to container in a JRockit VM. This can be worked around by building war in IDE, rather than depending on ASM to code-generate DBWSProvider.class file.
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
2.1.0
- Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format Design
- MOXy Mapping Extensions - Phase 6 complete
- Phase 7
- Inverse reference mapping
- Fragment mapping
- Transformation mapping
- MOXY Dynamic Persistence Design
- Bootstrapping from Schema
- Phase 10 complete
- Exception - Enum support (requiring core Dynamic Persistence change)
- Need to complete testing and check-in
- Phase 10 complete
- Issue creating plugin project for XJC library - working through alternative solutions.
- Bootstrapping from Schema
- JAXB2.2 Compliance
- Down to one failing test - a TCK challenge has been issued against this.
- Checked in fixex for other issues
- JAXB2.1 TCK - some tests failing with JDK1.6.0_18
- OSGi, Server testing
- Discussion with Dev, QA teams to improve the level of server and OSGi testing we have for MOXy and SDO components.
Dynamic Persistence
EclipseLink Incubator
EclipseLink/Development/Incubation
- EclipseLink/Development/Incubator/Extensions
- NetWeaver platform promotion.
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.