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

Latest revision as of 11:00, 12 September 2013

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 June 6, 2013

11 am EST, Thurs

Ad Hoc

Release Planning

2.3.4 - No Planned release
- M2 - May 22 (patch request)
- M3 - June 27 (patch request)
2.5.1 - (Milestones 3rd Wednesday of Month)
- M1 - June 20 (Complete)
- RC1 - Aug 24 (Complete)
2.6.0
- M1 - June 20 (Complete)
- M2 - Aug 16 (Complete)
Kepler SR1 - September 27
- RC1+1 - Aug 19 (2.5.1 M1)
- RC2+1 - Sept 2
- RC3+1 - Sept 9 (2.5.1 RC1)
- RC4+1 - Sept 16
Luna - GA June 2014
- M1+1 - Aug 19 (2.6.0 M2)
- M2+1 - Sept 30

Build

RoadMap

Sept 12, 2013:

EclipseLink to Maven Central
- SonatypeOSS "Milestone" process needs refining and testing. (2.5.1 M1)
Build cleanup
- Post-vacation revealed some process holes.
  - Closed most of them.
  - Working on reactivating common build user
  - Documenting the rest
Migration to Maven
- Currently investigating means of generating eclipselink.jar from bundles
- seems separate reactor means separate run - issues with OSGi/non-OSGi dependencies
Utilize maven to grab dependencies (revamp compdeps solution)
- partial solution using Tycho to accept Maven dependencies
  - still may need another step to get locally for tesing
    - working on prototype
Issues targeted for investigation:
- Select Bundle not working with OpenJDK
- JPA-RS testing not running at Eclipse

QA

Sept 5-12 , 2013:

Nightly Triage
- Manually re-run DBWS testing on JavaSE with Oracle-11.2.0.3 DB and MySQL-5.6 within both 2.5.1 and 2.6.0, provide debug info to dev for some new failures
Testing
- 2.5.1 RC1 manual testing -- complete
- Added GF 4.0.1 testing to nightly for 2.5.1 -- will triage results
Test Dev
- GF4-web profile: continue working on reconfiguring JAXRS-test to use WAR file deployment (instead of EAR) -- complete
Infra
This week:
- Continue to monitor 2.5.1 test results
[Backlog | TLQA-ELBacklog]

JPA

MOXy / SDO

RoadMap

2.6

JSON Schema Generation
MOXy footprint reduction
- Reduce install size and simplify bundling with 3rd party products.
Support Java API for JSON processing
- JSR-353 is the Java standard for producing and consuming JSON introduced with Java EE 7. MOXy has been updated to marshal/unmarshal using the JSON API

DBWS

DBWS Development

DBWS Roadmap

2.6

JPA metadata generator
- Consolidate implementation, usable by DBWS & JPA-RS
- Support JDBC datatypes, PL/SQL, NoSQL
DDL Parser metadata generation
- Document current usage, to feed into Service Generation functionality

EclipseLink Incubator

EclipseLink/Development/Incubation

Time to create separate sub-project for incubator
- Increase community of committers
- Try out GIT & eGit/jGit tooling in incubator?

Documentation

EclipseLink 2.4.x library: http://www.eclipse.org/eclipselink/documentation/2.4/ (refreshed)
EclipseLink 2.5.x doc library: available: http://www.eclipse.org/eclipselink/documentation/2.5/ (in progress)
Updated all doc custom search engines: http://www.eclipse.org/eclipselink/documentation/
All docs remain in a rolling review:
- Concepts Guide
- Solutions Guide (includes installation and migration information)
- JPA Extensions Reference
- Developing JAXB with EL MOXy
- Developing with EL DBWS

Bug Status

Bug reports

Foundation and JPA

Bugs By Target and Priority

Resolved Bugs

Created Bugs

EclipseLink/Development/DevMeetings/ArchiveBugReports

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

@@ Line 23: / Line 23: @@
-== Agenda Apr 1, 2010  ==
+== Agenda June 6, 2013  ==
-[http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=1&year=2010&hour=11&min=0&sec=0&p1=188 11 am EST, Thurs Apr 1st, 2010]
+[http://www.timeanddate.com/worldclock/fixedtime.html?month=09&day=13&year=2012&hour=11&min=0&sec=0&p1=188 11 am EST, Thurs]
 === Ad Hoc ===
 == Release Planning ==
-* 1.1.4: Not yet scheduled - Planned final patch for 1.1.x stream
+* 2.3.4 - No Planned release
-** wait for community to request.
+** M2  - May 22 (patch request)
-* 2.0.2: Proposed date: April 21st
+** M3  - June 27 (patch request)
-* [http://wiki.eclipse.org/EclipseLink/Development/2.1 2.1] [[Helios]]
+* 2.5.1 - (Milestones 3rd Wednesday of Month)
-** http://www.eclipse.org/projects/project-plan.php?projectid=rt.eclipselink
+** M1  - June 20 (Complete)
-* Galileo SR2 - February 26th/2010
+** RC1 - Aug  24 (Complete)
-** RC1+0 Jan 18/10: EclipseLink 1.1.3 (latest Milestone or Release)
+* 2.6.0
-*** 1.1.3 has been put into SR2
+** M1 - June 20 (Complete)
+** M2 - Aug  16 (Complete)
+* Kepler SR1 - September 27
+** RC1+1 - Aug  19 (2.5.1 M1)
+** RC2+1 - Sept 2
+** RC3+1 - Sept 9  (2.5.1 RC1)
+** RC4+1 - Sept 16
+* Luna - GA June 2014
+** M1+1 - Aug  19 (2.6.0 M2)
+** M2+1 - Sept 30
-== QA ==
+== Build ==
+[http://wiki.eclipse.org/EclipseLink/Build/Roadmap RoadMap]
-Mar 26 - April 1, 2010:
+Sept 12, 2013:
+* EclipseLink to Maven Central
+** SonatypeOSS "Milestone" process needs refining and testing. (2.5.1 M1)
+* Build cleanup
+** Post-vacation revealed some process holes.
+*** Closed most of them.
+*** Working on reactivating common build user
+*** Documenting the rest
+* Migration to Maven
+** Currently investigating means of generating eclipselink.jar from bundles
+** seems separate reactor means separate run - issues with OSGi/non-OSGi dependencies
+* Utilize maven to grab dependencies (revamp compdeps solution)
+** partial solution using Tycho to accept Maven dependencies
+*** still may need another step to get locally for tesing
+**** working on prototype
+* Issues targeted for investigation:
+** Select Bundle not working with OpenJDK
+** JPA-RS testing not running at Eclipse
-* Nightly Results
+== QA  ==
-** 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
-* 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 ==
+Sept 5-12 , 2013:
-* 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:
+* Nightly Triage
+** Manually re-run DBWS testing on JavaSE with Oracle-11.2.0.3 DB and MySQL-5.6 within both 2.5.1 and 2.6.0, provide debug info to dev for some new failures
+* Testing
+** 2.5.1 RC1 manual testing -- complete
+** Added GF 4.0.1 testing to nightly for 2.5.1 -- will triage results
+* Test Dev
+** GF4-web profile: continue working on reconfiguring JAXRS-test to use WAR file deployment (instead of EAR) -- complete
+* Infra
+**
+* This week:
+** Continue to monitor 2.5.1 test results
+* [Backlog | TLQA-ELBacklog]
 == JPA  ==
-Mar 25
+--
-.1.0
+== MOXy / SDO  ==
-* Advanced JPA config
+[http://wiki.eclipse.org/EclipseLink/Development/MOXy RoadMap]
-** Virtual access
-*** Dynamic persistence requirment
-* Advanced JPA Querying
-** wiki started with prioritized feature list (http://wiki.eclipse.org/EclipseLink/Development/2.1/AdvancedJPA_Queries)
-** Downcast queries implementation
-** Fetch Group
-* Bugs with Votes
+.6
+* [http://wiki.eclipse.org/EclipseLink/Development/404452 JSON Schema Generation]
+* [http://wiki.eclipse.org/EclipseLink/DesignDocs/384399 MOXy footprint reduction]
+**  Reduce install size and simplify bundling with 3rd party products.
+* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=405161 Support Java API for JSON processing]
+** JSR-353 is the Java standard for producing and consuming JSON introduced with Java EE 7. MOXy has been updated to marshal/unmarshal using the JSON API
 == DBWS  ==
 [http://wiki.eclipse.org/EclipseLink/Development/DBWS DBWS Development]
-.0.2
+[http://wiki.eclipse.org/EclipseLink/Development/DBWS/RoadMap DBWS Roadmap]
-* No remaining bugs
-.1.0
+.6
-* 290156 Validate SOAP message elements
+*JPA metadata generator
-* Scoping out potential EclipseLink feature work
+**Consolidate implementation, usable by DBWS &amp; JPA-RS
-** Improved Sparse Merge support (an 'Update' operation currently requires the instance to be fully specified in the SOAP message)
+**Support JDBC datatypes, PL/SQL, NoSQL
+*[http://wiki.eclipse.org/EclipseLink/Development/DBWS/MetadataGenerationFromDDLMetaModel DDL Parser metadata generation]
-* Bug - Using DBWS in JRockit environment due to ASM generated class incompatibility
+**Document current usage, to feed into Service Generation functionality
-# ASM <br/> Each DBWS web service <tt>.war</tt> file contains an ASM-generated class that implements the JAX-WS <code>javax.xml.ws.Provider</code> API
-<source lang="java5">
-public interface Provider<T> {
-     T invoke(T request) {
-         return ...
-     }
-}
-</source>
-For DBWS, the generic <code><T></code> is bound to <code>javax.xml.soap.SOAPMessage</code>. In addition, the generated class requires a number annotations to indicate information about WSDL, target XML namespace, resource injection and lifecycle methods:
-<source lang="java5">
-//Java extension libraries
-import javax.annotation.PostConstruct;
-import javax.annotation.PreDestroy;
-import javax.annotation.Resource;
-import javax.servlet.ServletContext;
-import javax.xml.soap.SOAPMessage;
-import javax.xml.ws.BindingType;
-import javax.xml.ws.Provider;
-import javax.xml.ws.ServiceMode;
-import javax.xml.ws.WebServiceContext;
-import javax.xml.ws.WebServiceProvider;
-import static javax.xml.ws.Service.Mode.MESSAGE;
-//EclipseLink imports
-import org.eclipse.persistence.internal.dbws.ProviderHelper;
-@WebServiceProvider(
-    wsdlLocation = "WEB-INF/wsdl/eclipselink-dbws.wsdl",
-    serviceName = {SERVICE NAME},
-    portName = {SERVICE NAME + "Port"},
-    targetNamespace = {SERVICE NAMESPACE}
-)
-@ServiceMode(MESSAGE)
-public class DBWSProvider extends ProviderHelper implements Provider<SOAPMessage> {
-    public  DBWSProvider() {
-        super();
-    }
-    @Resource
-    protected WebServiceContext wsContext;
-    @PostConstruct
-    public void init() {
-        ...
-    }
-    @Override
-    public SOAPMessage invoke(SOAPMessage request) {
-        if (wsContext != null) {
-            setMessageContext(wsContext.getMessageContext());
-        }
-        return super.invoke(request);
-    }
-    @PreDestroy
-    public void destroy() {
-        ...
-    }
-</source>
-A <tt>.war</tt> file containing <code>_dbws.DBWSProvider</code> will deploy to a WebLogic server fine, but when the <code>invoke(request)</code> method is hit, a <tt>.dump</tt> file is generated for JRockit JVMs; the same <tt>.war</tt> file, deployed to the same WebLogic server running on the Sun JDK, works fine.
-The underlying problem is the version of ASM in <code>o.e.p.internal.libraries.asm</code> is 1.5.3. When I re-implemented the one class <code>o.e.p.tools.dbws.ProviderPackager</code> that does all the ASM work for the <code>DBWSBuilder</code>, the <tt>.war</tt> file works for both JRockit <b>and</b> Sun JVMs.
-There are no runtime-dependencies to ASM (1.5 or 3.n, internal or external) for generated <code>DBWSProvider</code>'s - this is solely a design-time requirement.
-The proposal is to include in the standalone install a copy of ASM 3.1 in ...\eclipse\utils\dbws (org.objectweb.asm_3.1.0.v200803061910.jar from Orbit) and generate a new jar file (eclipselink-dbwsutils-asm3.jar) that, if the user requires, can be placed <b>ahead</b> of the 'real' eclipselink-dbwsutils.jar file so that the new functionality can be used to generate a <tt>.war</tt> file that works with JRockit JVMs.
-For the EclipseLink installer, the issue is whether or not we can get a CQ thru the system in time for Helios/2.1
-== SDO / MOXy  ==
-.0.2
-* All 2.0.2 bugs resolved
-.1.0
-* 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]
-* JAXB2.2 Compliance
-** JAXB 2.1.12, 2.2 API, Impl jars submitted to Orbit
-** Need to determine whether new CQ is required for XJC, based on new Dynamic Persistence runtime dependency
-* 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 ==
-[http://wiki.eclipse.org/EclipseLink/Development/Dynamic Dynamic Persistence]
 == EclipseLink Incubator  ==
 [[EclipseLink/Development/Incubation]]
-* [[EclipseLink/Development/Incubator/Extensions]]
-** FetchPlan incubator active
+* Time to create separate sub-project for incubator
-*** Doug requesting help.
+** Increase community of committers
+** Try out GIT & eGit/jGit tooling in incubator?
 == Documentation ==
-*Working on automated doc build process (Rick & Eric)<br />If not possible, Rick is working on an automated  localized doc build process, and would simply post the daily doc builds
+*EclipseLink 2.4.x library: http://www.eclipse.org/eclipselink/documentation/2.4/ (refreshed)
-*Updated [http://wiki.eclipse.org/EclipseLink/Development/Documentation/Requirements Documentation Requirements and Build Proposal]
+*EclipseLink 2.5.x doc library: available: http://www.eclipse.org/eclipselink/documentation/2.5/ (in progress)
-*Several "chapters" currently stored in XML. More to come once the production/build process is finalized.
+* Updated all doc custom search engines: http://www.eclipse.org/eclipselink/documentation/
-*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.
+* All docs remain in a rolling review:
+** Concepts Guide
+** Solutions Guide (includes installation and migration information)
+** JPA Extensions Reference
+** Developing JAXB with EL MOXy
+** Developing with EL DBWS
 == Bug Status  ==

Breadcrumbs