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
m (→DBWS) |
m (→SDO / MOXy) |
||
| Line 139: | Line 139: | ||
* Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format [http://wiki.eclipse.org/EclipseLink/DesignDocs/293925 Design] | * Representation of JAXB Annotations and enhanced MOXy metadata in externalized 'eclipselink-oxm.xml' metadata format [http://wiki.eclipse.org/EclipseLink/DesignDocs/293925 Design] | ||
* MOXY Dynamic Persistence [http://wiki.eclipse.org/EclipseLink/Development/2.1/DynamicMOXy/296967 Design] | * MOXY Dynamic Persistence [http://wiki.eclipse.org/EclipseLink/Development/2.1/DynamicMOXy/296967 Design] | ||
| + | ** Phase 7 of development complete | ||
| + | ** Runtime dependency introduced on JAXB XJC (Schema-to-Java compiler). Issue creating plugin project for XJC library - may need to deliver MOXy dynamic persitence as a regular Java project (ie. would not be available through OSGi). | ||
| + | ** Phase 8 introduces enum support - will need core Dynamic Persistence support. | ||
* JAXB2.2 Compliance | * JAXB2.2 Compliance | ||
| − | ** | + | ** 3 tests remaining - fixes identified. |
| − | + | ||
* OSGi, Server testing | * OSGi, Server testing | ||
** Discussion with Dev, QA teams to improve the level of server and OSGi testing we have for MOXy and SDO components. | ** Discussion with Dev, QA teams to improve the level of server and OSGi testing we have for MOXy and SDO components. | ||
Revision as of 13:13, 7 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 1, 2010
11 am EST, Thurs Apr 1st, 2010
Ad Hoc
Release Planning
- 2.0.2: Proposed date: April 21st\
- Stream is now frozen. Showstoppers approved by Doug/Peter only.
- 2.1 Helios
QA
Mar 26 - April 1, 2010:
- Nightly Results
- 1.1.4 - JPA/Glassfish 2.0 jpql test failures - bug 307114
- 2.0.2 - no recent builds
- 1.2.0 - no recent builds
- trunk - JPA/J2SE tests hanging - investigating
- Last week
- Fixed Bugs
- 307404 - need to add JPA server testing on JBOSS EAP
- Ran SDO server tests on Websphere - passed
- EL 2.1 Advanced Query - FUNC support test spec 90%; Downcast - documents reviewed, reviewed example
- EL 2.1 Advanced JPA Config - reviewed feature docs, and the tests that have been added.
- Triage - 7 bugs filed
- Fixed Bugs
- This week
- Change SDO server tests to run on any app server
- Continue with EL 2.1 test dev work - Advanced querying, Advanced JPA config
- JAXB 2.2 - enable in nightly automation
- JAXB nightly tests - email notification not working - will fix
- JAXB osgi testing - investigation
- 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.
- RT is requesting we simplify how we are included in RT - siingle SDK
- 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 ?)
- As a team we need to decide:
- 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).
- Prototype complete.
- 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
JPA
Apr 1 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
- WDF tests broken by
- Advanced JPA config
- Virtual access
- Dynamic persistence requirment
- Virtual access
- 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 Dynamic Persistence Design
- Phase 7 of development complete
- Runtime dependency introduced on JAXB XJC (Schema-to-Java compiler). Issue creating plugin project for XJC library - may need to deliver MOXy dynamic persitence as a regular Java project (ie. would not be available through OSGi).
- Phase 8 introduces enum support - will need core Dynamic Persistence support.
- JAXB2.2 Compliance
- 3 tests remaining - fixes identified.
- 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.