Community
Participate
Working Groups
Examples will be stored in a hierarchical structure within the given development branch like: \trunk\examples\jpa\employee\eclipselink.examples.jpa.employee.xml Note that the leaf folder name should correspond to the Eclipse Java/PDE project name starting with eclipselink.examples. The remainder of the project name should indicate the physical folder hierarchy as well as provide a logical categorization to identify the purpose of the example or the feature being shown.
If we're planning on moving to OSGi centric PDE based development we should consider our project naming convention carefully. In the OSGi proof of concept I renamed all the projects (but not SVN folders to simplify diffing against MAIN) to the reverse domain structure, e.g., org.eclipse.persistence.jpa org.eclipse.persistence.moxy While this naming convention is not mandatory, it is considered "good form". I suggest we name all example projects "org.eclipse.persistence.example.*" so the proposed employee example would be: org.eclipse.persistence.example.jpa.employee.xml Note "example" is singular. I agree we can place all examples under "\trunk\examples\" so they can be versioned and tagged with the rest of the trunk. For examples of PDE project/bundle naming, open the "Plug-in Development" Perspective in the Eclipse IDE and select the "Plug-ins" view. All of the plugins you will find follow this naming convention.
We need to add Wiki guidelines for examples. - All example projects should have a Wiki URL. - Need to differentiate between examples, tutorials and how-tos. - Examples have checked-in SVN code (we need to watch that wiki-pasted code does not diverge from the SVN version). - Tutorials only have wiki-pasted or (downloadable Zip) code. - General sections on changing hardcoded db and pu parameters, creating the schema, populating the db, test case run order and db cleanup (in the case we dont drop tables and get a constraint violation on a rerun)
Updating priority due to revised bug categorization process. See the following page for details: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines#Priority_and_Target_Milestone If you feel the updated priority is incorrect, please send an email to eclipselink-users@eclipse.org.
>Note: directories - bin (SE) and build/classes (EJB/WAR) should not be checked into SVN >DDL generation can be left 1-time enabled for Derby (DDL scripts do not need to be supplied)
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
