Skip to main content
Jump to: navigation, search

Difference between revisions of "EclipseLink/Development"

(Links)
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
<td valign="top">
 
<td valign="top">
 
<table>
 
<table>
<tr>
 
<td>
 
=== Welcome to the <b>Eclipse Persistence Services Project (EclipseLink)</b> Development Home ===
 
This page is focussed on information about current development and development process for the comitters of the EclipseLink project.
 
</td>
 
</tr>
 
  
 
<tr>
 
<tr>
Line 61: Line 55:
  
 
* [[/Process|Contribution/Development Process]] - overview of development process
 
* [[/Process|Contribution/Development Process]] - overview of development process
* [[EclipseLink/Building| Building]] - how to build EclipseLink
+
* [[EclipseLink/Building| Building & Testing]] - how to build and test EclipseLink
* [[/Testing|Testing]] - how to test EclipseLink
+
* [[/Testing|Testing]] - more information on EclipseLink testing
  
 
* [[EclipseLink/Maven|Maven]] - EclipseLink in Maven
 
* [[EclipseLink/Maven|Maven]] - EclipseLink in Maven
Line 71: Line 65:
 
* [[EclipseLink/IPLog | IP Log, Dependencies]] - where all external contributions and dependencies must be tracked
 
* [[EclipseLink/IPLog | IP Log, Dependencies]] - where all external contributions and dependencies must be tracked
  
* [[EclipseLink/Bugs|Bugs and Enhancements]]
+
* [[EclipseLink/Development/Bugs|Bugs and Enhancements]]
  
 
====Resources, Documentation====
 
====Resources, Documentation====

Latest revision as of 13:04, 18 April 2015

Current Development

  • Development has moved from SVN to Git, see Git

Features, Bugs & Enhancements

Features and Enhancements will have a BugZilla enhancement associated with it. A design document will be created for each feature. A review of these docs will be initially done by mailing list (eclipselink-dev@eclipse.org) and by meeting if followup is required. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

Docs are usually not required for bug fixes. Prior to code being checked in, code reviews will be done through the mailing list (eclipselink-dev@eclipse.org).

EclipseLink Newsgroups & Mailing Lists

Links

  • Git - source code repository
  • Maven - EclipseLink in Maven

Resources, Documentation

Back to the top