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.
Difference between revisions of "EclipseLink/IPLog"
(→2.2 Contributions) |
(→Contributions) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The IP Project Log is a document that records code and non-code contributions. | + | The IP Project Log is a document that records code and non-code contributions. This log is now generated, and this wiki site is not longer used to track IP content. The steps for adding content can be found on this page, and [http://wiki.eclipse.org/Development_Resources/IP_Log here]. |
| + | The generated log can be found here: http://www.eclipse.org/projects/ip_log.php?projectid=rt.eclipselink | ||
| + | |||
| + | = IP LOG Process = | ||
| + | == Contributions == | ||
| + | |||
| + | * All contributions from non committers start out as either a comment on a bug, or an attachment to the bug. NOTE: the patch, or the comment with the suggested IP needs to be put in the bug by the contributor, and NOT a committer. | ||
| + | * If the contribution is included in a patch attached to the bug, set the '''iplog''' flag on the bug to '''attachment details''' page is set to (<font color="red">'''+'''</font>). Here is an [https://bugs.eclipse.org/bugs/attachment.cgi?id=160912&action=edit Example]. Note: The (<font color="red">'''+'''</font>) must be set on the patch contributed by the contributor, even if it is marked as obsolete. (unless the final patch contains NO ip from the original patch). | ||
| + | *Only set the '''iplog''' flag on the '''bottom right''' of the '''bug''' page to (<font color="red">'''+'''</font>) for bugs that contain IP contributions within the bug text. Here is an [http://bugs.eclipse.org/249667 Example]. | ||
| + | |||
| + | <!-- Do not modify in this comment - it is kept only for historical purposes. | ||
== Committers == | == Committers == | ||
A list of all the Committers, past and present, whose contribution is still active in the repository. | A list of all the Committers, past and present, whose contribution is still active in the repository. | ||
| Line 40: | Line 50: | ||
! Contributor | ! Contributor | ||
! Description | ! Description | ||
| + | |- | ||
| + | | November 30, 2010 || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=331352 Bug 331352] || files: 1 new, 1 modified, 85 loc || dminsky || Vikram Bhatia || Fix to OneToOneMapping buildObjectJoinExpression to handle the "is not null" scenario and not throw an exception | ||
| + | |- | ||
| + | | November 25, 2010 || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=331064 Bug 331064] || files: 1 new, 2 modified, 150 loc || dminsky || John Vandale || Fix to CommitManager to order object deletions by PK if uow.shouldOrderUpdates() == true | ||
| + | |- | ||
| + | | November 24, 2010 || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=328774 Bug 328774] || files: 4 new, 2 modified, 150 loc || gpelleti || Frank Schwarz || TABLE_PER_CLASS-mapped key of a java.util.Map does not work for querying | ||
|- | |- | ||
| October 27, 2010 || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=270762 Bug 270762] || files: 1 new, 14 modified, 370 loc || dminsky || Vikram Bhatia || Changes to mappings (weighting), normalization and mapping comparison to implement a predictable commit order | | October 27, 2010 || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=270762 Bug 270762] || files: 1 new, 14 modified, 370 loc || dminsky || Vikram Bhatia || Changes to mappings (weighting), normalization and mapping comparison to implement a predictable commit order | ||
| Line 617: | Line 633: | ||
* The Oracle JDBC (CQ 2437) optional '''works-with''' capabilities available for those users who wish to access advanced features of the Oracle database and therefore have the corresponding libraries available from their database distribution. The functionality that leverages the additional features is isolated within SVN at: /foundation/org.eclipse.persistence.oracle . Both the Eclipse projects and ANT targets provided enable users to build and test EclipseLink without these optional dependencies or if they want to use these they can configure either Eclipse IDE variables or customize ANT properties files to provide the location of their works-with Oracle JDBC libraries. | * The Oracle JDBC (CQ 2437) optional '''works-with''' capabilities available for those users who wish to access advanced features of the Oracle database and therefore have the corresponding libraries available from their database distribution. The functionality that leverages the additional features is isolated within SVN at: /foundation/org.eclipse.persistence.oracle . Both the Eclipse projects and ANT targets provided enable users to build and test EclipseLink without these optional dependencies or if they want to use these they can configure either Eclipse IDE variables or customize ANT properties files to provide the location of their works-with Oracle JDBC libraries. | ||
| + | '''Bold text''' | ||
| + | |||
| + | --> | ||
Revision as of 13:52, 14 December 2010
The IP Project Log is a document that records code and non-code contributions. This log is now generated, and this wiki site is not longer used to track IP content. The steps for adding content can be found on this page, and here.
The generated log can be found here: http://www.eclipse.org/projects/ip_log.php?projectid=rt.eclipselink
IP LOG Process
Contributions
- All contributions from non committers start out as either a comment on a bug, or an attachment to the bug. NOTE: the patch, or the comment with the suggested IP needs to be put in the bug by the contributor, and NOT a committer.
- If the contribution is included in a patch attached to the bug, set the iplog flag on the bug to attachment details page is set to (+). Here is an Example. Note: The (+) must be set on the patch contributed by the contributor, even if it is marked as obsolete. (unless the final patch contains NO ip from the original patch).
- Only set the iplog flag on the bottom right of the bug page to (+) for bugs that contain IP contributions within the bug text. Here is an Example.