openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r1415738 [7/9] - in /openjpa/site/trunk: content/ original.cwiki.content/
Date Fri, 30 Nov 2012 16:56:08 GMT
Added: openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-1.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-1.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-1.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-1.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,73 @@
+h2. Logo Submissions
+
+Logos submitted for Round #1 voting from July 1 - July 9:
+
+# !http://os.oles.biz/openjpa-logo-ideas/variant1.png|vspace=5! - Georgi Naplatanov - gosho_at_oles_biz
+# !http://os.oles.biz/openjpa-logo-ideas/variant2.png|vspace=5! - Georgi Naplatanov - gosho_at_oles_biz
+# !http://os.oles.biz/openjpa-logo-ideas/variant3.png|vspace=5! - Georgi Naplatanov - gosho_at_oles_biz
+# !http://os.oles.biz/openjpa-logo-ideas/variant4.png|vspace=5! - Georgi Naplatanov - gosho_at_oles_biz
+# !http://os.oles.biz/openjpa-logo-ideas/variant5.png|vspace=5! - Georgi Naplatanov - gosho_at_oles_biz
+# http://os.oles.biz/openjpa-logo-ideas/idea1.svg - Georgi Naplatanov - gosho_at_oles_biz
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo1.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://issues.apache.org/jira/secure/attachment/12412198/openjpa-logo-1.png|vspace=5! - Pinaki Poddar - ppoddar_at_apache_org
+# !http://issues.apache.org/jira/secure/attachment/12412197/openjpa-logo-2.png|vspace=5! - Pinaki Poddar - ppoddar_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo2.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo3.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo4.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo5.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo6.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo7.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+# !https://issues.apache.org/jira/secure/attachment/12412745/openjpa-v002-website.png|vspace=5! - Pid - p_at_pidster_com
+# !https://issues.apache.org/jira/secure/attachment/12412738/openjpa-v007-website.png|vspace=5! - Pid - p_at_pidster_com
+# !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo8.png|vspace=5! - Donald Woods - dwoods_at_apache_org
+
+
+\\
+
+h2. Votes
+
+|| Name || Date || First || Second || Third || Comments ||
+| Albert Lee | 20090702 | #16 | #14 | #7 |  |
+| Ravi Palacheria | 20090702 | #15 | #8 | #9 |  |
+| Jeremy Bauer | 20090702 | #18 | #16 | #14 |  |
+| Daryl Stultz | 20090702 | #7 | #2 |  | #7 tighten up the kerning between the P and A. #2 but I don't like the way the "apache project" is over the circle. |
+| Ognjen Blagojevic | 20090703 | #8 | #7 |  | #8 needs a bit softer letter edges |
+| David Beer | 20090703 | #16 | #17 | #18 |  |
+| C N Davies | 20090703 | #13 | #4 |  |  |
+| Milosz Tylenda | 20090705 | #7 |  |  | A could stay a bit closer to P |
+| Kevin Sutter | 20090706 | #18 | #13 | #10 | Thanks, Donald, for #18 update. |
+| Michael Dick | 20090706 | #7 | #14 | #15 |  |
+| Craig Russell | 20090706 | #14 | #10 | #7 | I'd still like to see the "O" with the feather and arrows used in #14, with the font (not the boxes and bubbles) used in #13; any chance of seeing that one?   |
+| Donald Woods | 20090707 | #18 | #16 | #13 |  |
+| Pid | 20090708 | #17 | #16 | #18 |  |
+| Marco Schwarz | 20090708 | #14 | #13 | #7 |  |
+
+\\
+
+h2. Voting Results
+
+|| Logo || First || Second || Third || Total Points ||
+|  1 | 0 | 0 | 0 |  0 |
+|  2 | 0 | 1 | 0 |  2 |
+|  3 | 0 | 0 | 0 |  0 |
+|  4 | 0 | 1 | 0 |  2 |
+|  5 | 0 | 0 | 0 |  0 |
+|  6 | 0 | 0 | 0 |  0 |
+|  7 | 3 | 1 | 3 | 14 |
+|  8 | 1 | 1 | 0 |  5 |
+|  9 | 0 | 0 | 1 |  1 |
+| 10 | 0 | 1 | 1 |  3 |
+| 11 | 0 | 0 | 0 |  0 |
+| 12 | 0 | 0 | 0 |  0 |
+| 13 | 1 | 2 | 1 |  8 |
+| 14 | 2 | 2 | 1 | 11 |
+| 15 | 1 | 0 | 1 |  4 |
+| 16 | 2 | 3 | 0 | 12 |
+| 17 | 1 | 1 | 0 |  5 |
+| 18 | 3 | 0 | 2 | 11 |
+
+
+First Round Winners:  #7, #16, #18, #14, #13
+
+\\
+

Added: openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-2.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-2.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-2.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---round-2.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,39 @@
+h2. Logo Submissions
+
+The results of the first round of voting can be found at - [OpenJPA Logo Contest - Round 1]
+
+The following are the finalists for Round 2 of voting from July 9 - 14:
+
+# - !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo1.png|vspace=5! - #7 by Donald Woods - dwoods_at_apache_org
+# - !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo5.png|vspace=5! - #13 by Donald Woods - dwoods_at_apache_org
+# - !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo6.png|vspace=5! - #14 by Donald Woods - dwoods_at_apache_org
+# - !https://issues.apache.org/jira/secure/attachment/12412745/openjpa-v002-website.png|vspace=5! - #16 by Pid - p_at_pidster_com
+# - !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo8.png|vspace=5! - #18 by Donald Woods - dwoods_at_apache_org
+
+
+\\
+
+h2. Votes
+
+|| Name || First || Second || Third || Comments ||
+| Donald Woods | 1 | 2 | 4 |  |
+| Albert Lee | 4 | 3 | 1 |  |
+| Kevin Sutter | 2 | 5 | 4 |  |
+| Pid | 4 | 1 | 5 | The difference between 1 and 3 is slight. Perhaps they should be unified (a vote for one is a vote for either) |
+|C N Davies | 4 | | | |
+| Michael Dick | 1 | 4 | 3 | |
+| Daryl Stultz | 1 |  |  |  |
+| Jeremy Bauer | 1 | 4 | 5 | |
+
+\\
+
+h2. Voting Results
+
+|| Logo || First || Second || Third || Total Points ||
+| 1 | 4 | 1 | 1 | 15 |
+| 2 | 1 | 1 | 0 | 4 |
+| 3 | 0 | 1 | 1 | 3 |
+| 4 | 3 | 2 | 2 | 15 |
+| 5 | 0 | 1 | 2 | 4 |
+
+\\

Added: openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---run-off.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---run-off.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---run-off.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpa-logo-contest---run-off.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,44 @@
+h2. Logo Submissions
+
+The results of the first round of voting can be found at - [OpenJPA Logo Contest - Round 1]
+
+The results of the second round of voting can be found at - [OpenJPA Logo Contest - Round 2]
+
+The following are the finalists for a run-off round of voting.
+Please only submit one vote and each vote will only count for 1 point.
+
+# - !http://people.apache.org/~dwoods/openjpa/logos/openjpa-logo1.png|vspace=5! - #7, #1 by Donald Woods - dwoods_at_apache_org
+# - !https://issues.apache.org/jira/secure/attachment/12412745/openjpa-v002-website.png|vspace=5! - #16, #4 by Pid - p_at_pidster_com
+
+\\
+
+h2. Votes
+
+|| Name || Vote || Comments ||
+| Donald Woods | 1 |  |
+| Kevin Sutter | 1 |  |
+| Albert Lee | 2 |  |
+| Jeremy Bauer | 1 |  |
+| Marco Schwartz | 1 | |
+| Daryl Stultz | 1 | | 
+| Pinaki Poddar | 2 | |
+| Pid | 2 | |
+| Rick Curtis | 2 | |
+| Michael Simons | 1 | |
+| Craig Russell | 1 | |
+| Umberto Carrara | 1 | |
+| C N Davies | 2 | | 
+| Tim Watts | 2 | | 
+| Peter Henderson | 1 | | 
+| Ognjen Blagojevic | 1| |
+
+
+\\
+
+h2. Voting Results
+
+|| Logo || Votes ||
+| 1 | 10 |
+| 2 | 6 |
+
+\\

Added: openjpa/site/trunk/original.cwiki.content/openjpa-release-policy.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpa-release-policy.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpa-release-policy.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpa-release-policy.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,19 @@
+h1. OpenJPA Release Policy
+
+h3. Release Numbering
+The release number consists of three digits separated by decimal points, followed by an optional status e.g. 2.1.6-beta2. The first digit is the major release number; the second is the minor release number; the third is the patch number. The optional status is an indicator of the release status, e.g. -alpha2, -rc1, etc. Generally, the status indicator is only used for major releases, e.g. 1.0.0-rc1 but is available for any release at the release manager's discretion.
+
+h3. SNAPSHOT Releases
+During development of a release, nightly builds are typically done and published under the SNAPSHOT rubric. The SNAPSHOT will contain the latest result of building the release, regardless of the release status. For example, while developing release 2.1.6, the version 2.1.6-SNAPSHOT will be the latest result even though the status changes from -alpha, -alpha2, -beta, -beta2, -rc1, -rc2. The last nightly before release would still be 2.1.6-SNAPSHOT. 
+
+h3. Backward Compatibility
+Backward compatibility means that user programs compiled against one release will still compile and execute with another release. Generally, the objective is to maintain backward compatibility for minor releases and patch releases but not major releases. For example, 2.1.5 will execute when run with e.g. 2.1.6 but there is no guarantee that the reverse is true, i.e. that user programs compiled against 2.1.6 will compile or run against 2.1.5.
+
+h2. Major Release
+Major releases have the minor and patch numbers set to 0. Major releases contain functionality changes compared to earlier major releases and may break backward compatibility if necessary. Once a major release is issued, a branch is created for maintenance, replacing the patch number with "x". 
+
+h2. Minor Release
+Minor releases have the patch number set to 0. Minor releases contain functionality changes compared to earlier minor releases within the same major release, but do not break backward compatibility.
+
+h2. Patch Release
+Patch releases contain bug fixes compared to the previous patch, minor, or major release on which they are built. Patch releases increment the patch number compared to the most recent patch release. Backward compatibility is maintained.
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/openjpa-up-close-and-personal.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpa-up-close-and-personal.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpa-up-close-and-personal.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpa-up-close-and-personal.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,83 @@
+h2. Summer 2007 Meeting Information
+
+The meeting is on the 6th and 7th of August, 2007.
+
+h3. Agenda
+
+h4. Monday 6 August
+||Time||Title||Description||Presenter||Sponsor||Presentation||
+|9:30 - 10:00|Introductions| | | | |
+|10:00 - 12:00|OpenJPA Architecture|High-level walk-through of OpenJPA architecture, including all the maven modules and the major internal abstractions.|Patrick Linskey / Abe White|Patrick Linskey|[Microsoft PowerPoint|http://people.apache.org/~pcl/2007/08/OpenJPAArchitecture.ppt][notes|Architecture Notes]|
+|12:00 - 1:00|Lunch|BEA Cafeteria or elsewhere in the area| | | |
+|1:00 - 2:30|FindBugs Presentation|Discussion with Bill Pugh (FindBugs) about how best to use FindBugs on OpenJPA, including a focus on how to use it for "new" bugs as code changes come in, vs. fixing the issues that already exist.|Bill Pugh|Craig Russell|[notes|FindBugs Presentation Notes]|
+|3:00 - 4:30|Query Processor|There are a lot of query JIRA issues; some background might enable more people to help out|Marc Prud'hommeaux|Craig Russell|[Microsoft PowerPoint|http://people.apache.org/~mprudhom/OpenJPAQueryFramework.ppt.gz] [Apple Keynote|http://people.apache.org/~mprudhom/OpenJPAQueryFramework.key.zip]|
+|5:00 - 5:30|Day One Wrap-Up|Figure out how we want to change the schedule for the next day| | | |
+|7:00 - ???|Dinner and Socializing|Presumably in San Jose| |Patrick Linskey| |
+
+
+h4. Tuesday 7 August
+||Time||Title||Description||Presenter||Sponsor||Presentation||
+|9:30 - 10:00|Day Two Kick-Off / New Agenda Item Review|Discuss what we'd like to talk about today, what we'd like to focus on that came up yesterday, and other topics that have occurred to people since yesterday| | | |
+|10:00 - 10:30|JIRA triage| | |Craig Russell| |
+|10:30 - 11:00|XML column support| |Catalina Wei|Patrick Linskey| [^JPA XMLColumn Mapping.ppt]|
+|11:30 - 12:00|API Design and Forwards-Compatibility|OpenJPA has a number of APIs that we expect to be visible to developers. These should be stable over time, and should be well-designed to meet the needs of our developers. This is currently not always the case (OpenJPAEntityManagerFactory extends a billion interfaces, for example, our event frameworks sometimes require code changes for people who implement the event interfaces, and we use a combination of enums and symbolic constants even in our org.apache.openjpa.persistence interfaces). I'd like to discuss this to raise awareness about the issue, and also discuss how to improve things in the short term. I'd also like to bring up the idea of an API jar that should contain enough for the average development team to link against.|Patrick Linskey|Patrick Linskey|[APIDiscussionFollowUp]|
+|12:00 - 1:00|Lunch|BEA Cafeteria or elsewhere in the area| | | |
+|1:30 - 2:00|Fluid|SDO bindings to OpenJPA|Pinaki Poddar| | |
+|2:15 - 2:45|Where to next?|OpenJPA 1.0, OpenJPA 1.1, JPA 2.0, SDO, etc.| | | |
+|3:00 - 3:45|Joins|There are a lot of issues around joins. In particular, subqueries seem to have issues. Discuss.|Abe White| | |
+|4:00 - 4:30|Metadata Resolution|Metadata lookup, classloaders, static caches, etc.| | | |
+|4:30 - 5:30|Update pathway|Updates, statement batching, reordering, etc.| | | |
+|5:30 - 6:00|Wrap-Up| | | | |
+
+|???|mappingtool|What do the options do? What about new options?| | | |
+
+The sponsor is the person proposing the agenda item, and is responsible for making sure that a given agenda item actually happens. The sponsor is not necessarily the person actually presenting / leading the discussion for a given item.
+
+h3. Venue
+
+[BEA headquarters in San Jose|http://maps.google.com/maps?hl=en&safe=off&client=firefox-a&q=bea&near=San+Jose,+CA&fb=1&cd=1&ie=UTF8&ei=QGmhRq7MBImUjQO27-nGCA&cid=37379388,-121922929,10392251224970924111&li=lmd&z=14&t=m] (near SJC)
+2315 North First Street
+San Jose, CA
+
+There is plenty of parking. The meeting room is in Building 1, which is the further-south building, abutting both First Street and Charcot Avenue. If you drive up First Street from the south, your best bet is to turn left on Charcot and then right into the parking lot. The receptionist in Building 1 will point you in the direction of the conference room.
+
+We have wireless internet available, so it should be easy to stay in touch in the break periods. Hopefully, all the sessions will be sufficiently riveting that nobody will be playing around on the internets during the sessions.
+
+Dial-in information:
+
+Toll Free Dial-In Number (US & Canada): (866) 484-4232
+International Dial-In Number: (702) 894-2358
+Conference Code: 1774023
+
+Webex information for day 1:
+Meeting number: 923 554 073 
+Meeting password: openjpa 
+https://bea.webex.com/bea/j.php?ED=94343937&UID=0 
+
+Webex information for day 2:
+Meeting number: 924 199 496 
+Meeting password: openjpa 
+https://bea.webex.com/bea/j.php?ED=94344132&UID=0 
+
+
+If you're new to webex meetings and plan to join via webex, it's probably a good idea to go to that link ahead of time to get things set up.
+
+
+h3. Attendee List / Local Transportation Logistics
+
+||Attendee||Location||Carpool needed?||Carpool space||Lodging||
+|Patrick Linskey|San Jose|No| 0 |Crowne Plaza 282 Almaden Blvd.|
+|Craig Russell|Mountain View |No | | |
+|Marc Prud'hommeaux|San Jose|No| |Crowne Plaza 282 Almaden Blvd.|
+|Christoph Bussler|San Jose|No| | |
+|Pinaki Poddar|San Francisco|Yes| |Galleria Park, 191 Sutter Street|
+| Bill Pugh | Palo Alto | No | No | | 
+| Michael Dick | Remote (Rochester, MN)  | No | No | |
+| Albert Lee | Remote (Rochester, MN)  | No | No | |
+| Teresa Kan | Remote (Rochester, MN)  | No | No | |
+| Kevin Sutter | Remote (Rochester, MN)  | No | No | Tuesday, Aug 07, Only |
+| Joe Weinstein | Moraga CA | No | No |
+| David Wisneski | San Jose CA | No | No | No |
+| Catalina Wei | San Jose CA | No | No | No |
+| Daniel Lee | San Jose CA | No | No | No |
+| Aditi Das | San Francisco CA | No | No | No |
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/openjpaeclipseenhancementbuilder.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpaeclipseenhancementbuilder.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpaeclipseenhancementbuilder.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpaeclipseenhancementbuilder.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,79 @@
+h1. OpenJPA Eclipse Tooling
+
+h2. How to use the OpenJPA Eclipse Tooling Builder for Bytecode Enhancement
+
+Once you have [installed the OpenJPA Eclipse tooling|OpenJPAEclipseInstallation], here is how to add the Bytecode Enhancement Builder to a Java project:
+
+# right-click on Project, click "Add/Remove Bytecode Enhancer"
+# in the Enable OpenJPA dialog which will be shown: (TBD: Attach screenshot here, once ugly [OPENJPA-1521|https://issues.apache.org/jira/browse/OPENJPA-1521] is resolved?)
+## choose if OpenJPA libraries should be added to project, this will copy the OpenJPA JARs from the Eclipse plug-in into a lib directory of the Java project, and add them as Referenced Libraries. (In a normal existing project you'll already have them via Maven or whatever so you'll not use / want to deactivate this; for new or test projects this is convenient.)
+## choose enhancement options, if you need any. These are the [same options as the CLI PCEnhancer supports|http://openjpa.apache.org/builds/latest/docs/manual/ref_guide_pc_enhance.html#ref_guide_pc_enhance_build].
+# menu Project > Properties (or right-click on Project > Properties) should now show the "OpenJPA PC-Enhancer Project Builder" added after the usual "Java Builder"
+# when Eclipse builds (compiles) the project, classes will now be byte-code enhanced
+
+
+h3. Known Limitations
+
+* persistence.xml is ignored, the plug-in / builder only looks for annotations (@Entity, @MappedSuperclass, @Embeddable, @ManagedInterface) to decide if a class actually needs enhancement
+* any error markers (the lines shown in the Problems view) are on the .class resource, instead of on the source .java class, which would be more convenient
+* the Builder runs even on classes which are red and compilation issues, because the Eclipse compiler still tries to produce a .class file, and may log weird error messages in that case
+
+
+h3. Troubleshooting, Tips & Recommendations
+
+* If the Builder has trouble during enhancement, it normally logs useful messages / exception stack traces to the Eclipse Error Log. Use menu Window > Show View > Error Log to display it. If you don't have the Error Log view, this could be because you have an Eclipse with the PDE (Plug-in Development Environment), get that. The Eclipse Error Log can also be exported from this view, e.g. to send it to the mailing list.  Further debugging & informational log messages can be enabled via the .project file, see below.
+
+* If your Eclipse dies due to "java.lang.OutOfMemoryError: Java heap space" / "java.lang.OutOfMemoryError: PermGen space" issues, you may need to add e.g. "-XX:PermSize=64m -XX:MaxPermSize=256m -Xms128m -Xmx512m" to your eclipse.ini (each option on a separate line) for the enhancement builder
+
+* In order to be sure that you're actually using build time enhancement, and not enhancing dynamically at run-time, you may wish to set the openjpa.RuntimeUnenhancedClasses=unsupported property in your persistence.xml or wherever you bootstrap OpenJPA (see [Omitting the OpenJPA enhancer|http://openjpa.apache.org/builds/latest/docs/manual/ref_guide_pc_enhance.html#ref_guide_pc_enhance_unenhanced_types])
+
+
+h3. Options
+
+* More verbose logging for the Builder can be enabled via a configuration option in .project.  This option is only intended for troubleshooting & debugging, because it seems to significantly (!) slow down the builder, and something goes wrong with the Progress view (Monitor stuff) causing it to not update correctly anymore, and appear to keep running (although it's not).
+
+{code:xml}
+<projectDescription>
+...
+    <buildSpec>
+...
+        <buildCommand>
+            <name>org.apache.openjpa.eclipse.OpenJPAEnhancerBuilder</name>
+            <arguments>
+                <dictionary>
+                    <key>debugLogs</key>
+                    <value>true</value>
+                </dictionary>
+{code}
+
+The debugLogs = true will lead to message such as these to be shown in the Error Log (the order sometimes appears to get messed up) :
+
+{code}
+OpenJPA Enhancement (Full Build, collecting resources) took 0ms, found 3 classes potentially needing enhancement
+OpenJPA Enhancer ran on but did not have to bytecode enhance /test-project/bin/ch.vorburger.jpa/SomeEntityTest.class
+OpenJPA Enhancer ran on and actually bytecode enhanced /test-project/bin/ch.vorburger.jpa/SomeEntity.class
+OpenJPA Enhancer ran on but did not have to bytecode enhance /test-again/bin/ch.vorburger.jpa/NotToEnhance.class
+OpenJPA Enhancement (Full Build) took 47ms, for 3 potential classes, of which 1 were actually enhanced
+{code}
+
+* The builder has been written with efficiency in mind and underwent some profiling & optimization, e.g. it correctly does only Incremental Builds when possible.  However, for projects with a lot of classes, this Builder may slow down the project. This is because it still has to byte-code inspect (load and analyze) each .class to determine if it needs enhancement.  If the JPA entities in your project follow some naming convention (e.g. all ending in *Entity, or all in a certain package), then the builder can be configured to "match" only certain classes using Ant-like patterns, by manually adding the following to the existing .project file of the Eclipse Java project:
+
+{code:xml}
+<projectDescription>
+...
+    <buildSpec>
+...
+        <buildCommand>
+            <name>org.apache.openjpa.eclipse.OpenJPAEnhancerBuilder</name>
+            <arguments>
+                <dictionary>
+                    <key>include1</key>
+                    <value>**/*Entity.class</value>
+                </dictionary>
+                <dictionary>
+                    <key>include2</key>
+                    <value>**/*EntityRef.class</value>
+                </dictionary>
+{code}
+
+* The above two options can be mixed by adding several <dictionary> inside the <arguments>.
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/openjpaeclipseinstallation.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpaeclipseinstallation.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpaeclipseinstallation.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpaeclipseinstallation.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,20 @@
+h1. OpenJPA Eclipse Tooling
+
+{info:title=Eclipse Update Site}
+http://people.apache.org/~dwoods/openjpa/devtools/updatesite/ is the current Update Site of the OpenJPA Eclipse Tooling. (It will probably still change.)
+{info}
+
+h2. How to install the OpenJPA Eclipse Tooling
+
+# Get Eclipse min. version 3.4
+# Install the OpenJPA Eclipse Tooling feature from the URL shown above
+## For Eclipse v3.4:
+### menu Help > Software Updates, click "Add Site..."
+### Copy/paste the URL above into Location, and "OK"
+### Check the OpenJPA Eclipse Feature, and "Install..."
+### Click "Next", accept the terms of the license agreement, Finish.
+### Restart Eclipse
+## For Eclipse v3.5:
+### *TBD*
+# FYI, menu Help > About > Plug-in Details should now show plug-ins with names "OpenJPA ..."
+# Go to [How to use the OpenJPA Eclipse Tooling Builder for Bytecode Enhancement|OpenJPAEclipseEnhancementBuilder] to see how to use this thing

Added: openjpa/site/trunk/original.cwiki.content/openjpaeclipsetoolingdevandbuild.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/openjpaeclipsetoolingdevandbuild.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/openjpaeclipsetoolingdevandbuild.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/openjpaeclipsetoolingdevandbuild.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,19 @@
+h1. OpenJPA Eclipse Tooling
+
+h2. How to develop on and build the OpenJPA Eclipse Tooling
+
+h3. IDE
+
+# get Eclipse with PDE
+# check out the https://svn.apache.org/repos/asf/openjpa/devtools/trunk/ (not just the individual project directories, but really the trunk, so that you also have the pom.xml at the root...).  If you use Subversive (or Subclipse) from within Eclipse to do the check-out, you'll have to remove the project from the workspace again after checkout, without delete on disk, so that you can import the individual projects in the next step.
+# open the individual projects in Eclipse (org.apache.openjpa.eclipse.feature, org.apache.openjpa, org.apache.openjpa.eclipse, openjpa-eclipse-testproject, org.apache.openjpa.eclipse.tests, org.apache.openjpa.eclipse.site) - _*requires correct .project and .classpath files currently missing from SVN*_
+
+
+h3. Headless Maven-based build (without requiring Eclipse IDE)
+
+# download Maven 3.0 from http://maven.apache.org/download.html.  Please note and make sure you do get & use Maven 3.0 (latest at the time of writing this Maven 3.0-alpha-6), and not just a Maven 2.2.1, which will NOT WORK.
+# check-out the https://svn.apache.org/repos/asf/openjpa/devtools/trunk/ (not just the individual project directories, but really the trunk, so that you also have the pom.xml at the root...)
+# do a "mvn install" at the root.  This will be VERY SLOW at first invocation, as it downloads LOT'S (really; including many Eclipse artefacts) into your local maven repo. Subsequent calls will as usual be much faster.
+# in the directory "org.apache.openjpa.eclipse.site/target/site" there will be a completely ready Eclipse Update Site (which is what gets be pushed to some HTTP server and the URL of which is given to end-users to install the whole thing)
+
+This should ideally be set-up on a public build server, e.g. on the http://hudson.zones.apache.org/hudson/ ?

Added: openjpa/site/trunk/original.cwiki.content/opentrader.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentrader.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentrader.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentrader.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,89 @@
+h1. OpenTrader: a transactional, web application with Google Web Toolkit, OpenJPA/Slice on Tomcat
+
+!OpenTrader-login.gif!
+
+
+OpenTrader is a sample web application to demonstrate integration of Google Web Toolkit (GWT) and OpenJPA running in Tomcat Servlet Container. These pages describe various aspects of this end-to-end application. The following sections are fairly independent of each other and can be followed as such based on your interest.
+ 
+* [Architecture|OpenTraderArchitecture] and core design goals 
+* The [computing environment|OpenTraderEnvironment] requirement
+* Developing a [GWT Client|OpenTraderClient]
+* Developing a [JPA based Server|OpenTraderServer]
+* [Communication|OpenTraderCommunication] between the components
+* [Building|OpenTraderBuild] the application
+* [Deploying|OpenTraderDeploy] the application
+
+GWT takes a position that is a significantly unique among the multitude of frameworks available to build a browser based client. GWT framework is based on several key concepts:
+
+* an asynchronous RPC protocol for communication between web client and server. Such asynchronous RPC is popularized by AJAX (Asynchronous JavaScript and XML) since last several years.
+* a cross-compiler that converts Java to JavaScript. This is the most critical component in the framework as it allows the client be written completely in Java. Besides adding a comfort layer for Java developers, the cross-compiler solves one of the most complex issue of browser based clients namely cross-browser compatibility. The cross-compiler generates separate JavaScript targeted to prominent browsers and the framework knows to activate the appropriate JavaScript based on the particular browser a client is using.
+* a library of interactive visual widgets such as dialog boxes, combo-boxes, tables etc. This Java based library realizes the widget as the elements of a Document Object Model (DOM) for a browser to render them in HTML. For example, an instance of {{com.google.gwt.user.client.ui.FlexTable}} urns into a {{<table>}} in the displayed HTML page by the framework. The widget library not only provides rendering support, it also comes with a event dispatching model for the client application to handle the user interaction. 
+
+OpenTrader - the sample example described in these pages - demonstrates how to develop a GWT client for a transactional, server application based on Java Persistence API (JPA). This example is somewhat more involved than a typical AddressBook example in terms of the complexity of the domain model, the transactional functions of the server as well as the interaction between multiple widgets in the client. Also the sample application covers a realistic use case where the core server application is defined independent of both GWT and JPA -- and then demonstrates how these two technologies are used to _implement_ an end-to-end service running inside a Tomcat Servlet Container. 
+
+
+
+Follow the steps to view OpenTrader source code, build the application, deploy it in your favorite application container and run it in your favorite browser.
+
+h3. 1. Get the source code
+
+   OpenTrader source code is available as one of the OpenJPA examples. Checkout the source files in a directory.
+
+   {{$ svn checkout   https://svn.apache.org/repos/asf/openjpa/trunk/openjpa-examples/opentrader}}
+
+  The source tree comes with 
+   * Ant build script: {{build.xml}} and {{build.properties}}
+   * Java source code for OpenTrader application under {{src/main/java}}
+   * GWT module descriptor  : {{OpenTrader.gwt.xml}} under {{src/main/java/org/apache/openjpa/trader}}
+   * Persistence descriptor : {{persistence.xml}} under {{src/main/resources/META-INF}}
+   * web descriptor         : {{web.xml}} under {{src/main/resources/WEB-INF}}
+   * cascading style sheet  : {{OpenTrader.css}} under {{src/main/resources/css}}
+   
+
+h3. 2. Build
+
+   To build OpenTrader you will require following other libraries. 
+   * *Google Web Toolkit*: We have built it with GWT version 2.0.4 which can be downloaded from [here|http://google-web-toolkit.googlecode.com/files/gwt-2.0.4.zip].
+   * *cobogw widget library*: Provides rounded panel not using them seems to be too un-cool. Download version 1.3.1 from [here|http://code.google.com/p/cobogw/downloads/list].
+   * and, of course, *OpenJPA libraries*: OpenJPA now comes with all its dependencies neatly packaged in a single jar including the JPA API. Download from [this site|http://www.apache.org/dyn/closer.cgi/openjpa/2.0.0/apache-openjpa-2.0.0-binary.zip]. 
+
+   h5. 2.1 Configure build environment 
+      
+      Edit  {{build.properties}} to point to the dependent libraries you have downloaded. The file contains the instructions as comments. 
+
+   h5. 2.2 Compile with Ant
+
+      Compile the application. Compilation involves three separate compilation process. First the plain old {{javac}} compilation. Followed by GWT cross-compiler that translates Java code into JavaScript. And finally OpenJPA compilation that adds few bytecodes to the persistent classes to manage their persistent behavior (which is also known as bytecode enhancement).
+     
+      {{$ ant compile}}
+
+      GWT Compiler takes ages. Even though it only compiles for a single browser (FireFox). This is controlled by the following directives in the module descriptor {{OpenTrader.gwt.xml}}
+
+     {code:xml}
+        <set-property name="user.agent" value="gecko1_8"/> 
+     {code}
+
+h3. 3. Run
+    
+    You can run either in _hosted_ mode - an environment provided by GWT to run within a Jetty container - or in a proper servlet container such as Tomcat, Geronimo or GlassFish or even heavy-duty ones such as WebSphere or Weblogic. In either case, you have to configure the {{persistence.xml}} found under {{src/main/resources/META-INF}}. This descriptor specifies the database used by OpenTrader.
+
+     {code:xml}
+        <property name="openjpa.ConnectionDriverName" value="com.mysql.jdbc.Driver"/>
+        <property name="openjpa.ConnectionURL" value="jdbc:mysql://localhost/exchange"/>
+        <property name="openjpa.ConnectionUserName" value="whoami"/>
+        <property name="openjpa.ConnectionPassword" value="secret"/>
+     {code}
+ 
+    Also edit the {{jdbc.driver}} in {{build.properties}} for the driver/database you have selected.
+
+    Now, for hosted mode, simply fire Ant as
+     {{$ ant devmode}}
+
+    This should again take a very long time and pop open a horrible looking Swing console titled *GWT Development Mode*. Go to *Development Mode* tab and click *Launch Default Browser*. On my FireFox browser, that opens up the page {{http://127.0.0.1:8888/OpenTrader.html?gwt.codesvr=127.0.0.1:9997}}. If all goes well, at this point your browser will prompt you with a welcome dialog box
+
+!OpenTrader-login.gif!
+
+Once you have entered OpenTrader, the browser application looks like 
+ !OpenTrader-screenshot.gif!
+    
+In this page, you can place a trade offer to sell or buy some stocks. To really commit a trade you will need a matching offer. Now as a trader offer can only match to another trader's offer, you need to open another browser page with a different name. In FireFox, the tab will show the Trader name. Now if one Trader makes an offer that match another Trader's offer, then clicking the {{Sell}} or {{Buy}} button will commit the trade and will appear on the Trading History Window. Also notice the Server Log window. That will display SQL issued for every action by the server. You will also notice SQL being logged even if you are not pressing any buttons. Thatis because the Market Data Panel (the one in th etop-left corner) is refreshing the market prices for the Stocks by a periodic call to the server. As the stock prices change, that change is reflected on the gain/loss column of the waiting trade offers. All this dynamic partial update occurs in the same browser page -- that is 
 what GWT offers.
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/opentraderarchitecture.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderarchitecture.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentraderarchitecture.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentraderarchitecture.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,30 @@
+State the design goals
+Describe the architecture
+
+One of the good practices of software development is to start with a set of basic requirements and then express these requirements more formally through a set the interfaces. So let us begin by listing the requirements for OpenTrader sample.  
+
+* a trader can offer to buy or sell stocks at a certain price 
+* an offer to sell(buy) a stock can be matched with matching offer(s) to buy(sell)
+* a pair of matching buy/sell offer can be committed as a trade
+
+Besides the functional requirements, let us define some non-functional goals
+
+* the trader will access the service from a browser
+* the service will use a relational database to record the committed trades 
+
+and then some purely technical goals
+
+* the browser-based client will be implemented using Google Web Toolkit
+* the service will be implemented using Java Persistence API
+
+
+
+
+
+GWT takes a position that is a significantly unique among the multitude of frameworks available to build a browser based client. GWT framework is based on several key concepts:
+
+    * an asynchronous RPC protocol for communication between web client and server. Such asynchronous RPC is popularized by AJAX (Asynchronous JavaScript and XML) since last several years.
+    * a cross-compiler that converts Java to JavaScript. This is the most critical component in the framework as it allows the client be written completely in Java. Besides adding a comfort layer for Java developers, the cross-compiler solves one of the most complex issue of browser based clients namely cross-browser compatibility. The cross-compiler generates separate JavaScript targeted to prominent browsers and the framework knows to activate the appropriate JavaScript based on the particular browser a client is using.
+    * a library of interactive visual widgets such as dialog boxes, combo-boxes, tables etc. This Java based library realizes the widget as the elements of a Document Object Model (DOM) for a browser to render them in HTML. For example, an instance of com.google.gwt.user.client.ui.FlexTable urns into a <table> in the displayed HTML page by the framework. The widget library not only provides rendering support, it also comes with a event dispatching model for the client application to handle the user interaction.
+
+OpenTrader - the sample example described in these pages - demonstrates how to develop a GWT client for a transactional, server application based on Java Persistence API (JPA). This example is somewhat more involved than a typical AddressBook example in terms of the complexity of the domain model, the transactional functions of the server as well as the interaction between multiple widgets in the client. Also the sample application covers a realistic use case where the core server application is defined independent of both GWT and JPA – and then demonstrates how these two technologies are used to implement an end-to-end service running inside a Tomcat Servlet Container. 

Added: openjpa/site/trunk/original.cwiki.content/opentraderbuild.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderbuild.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentraderbuild.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentraderbuild.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1 @@
+Build instructions
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/opentraderclient.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderclient.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentraderclient.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentraderclient.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1 @@
+Describe the client side development
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/opentradercommunication.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentradercommunication.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentradercommunication.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentradercommunication.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,2 @@
+Describe the communication between client and server
+between client communications
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/opentraderdeploy.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderdeploy.cwiki?rev=1415738&view=auto
==============================================================================
    (empty)

Added: openjpa/site/trunk/original.cwiki.content/opentraderenvironment.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderenvironment.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentraderenvironment.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentraderenvironment.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1 @@
+What do we need to download
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/opentraderserver.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/opentraderserver.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/opentraderserver.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/opentraderserver.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1 @@
+Describe the server
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/overview.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/overview.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/overview.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/overview.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,5 @@
+{excerpt:hidden=true}Overview{excerpt}
+
+h1. Overview
+
+{children:all=true|excerpt=true} 
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/performance-guide.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/performance-guide.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/performance-guide.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/performance-guide.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,26 @@
+{excerpt:hidden=true}OpenJPA Performance Guide{excerpt}
+
+h1. OpenJPA Performance Guide
+
+OpenJPA has numerous configuration properties that apply to many different use cases. The complete list of properties can be found in the most current [user manual|http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_optimization]. The remainder of this guide is going to walk through the properties that will generally provide the most performance improvement. 
+
+h2. Caching
+
+h5. DataCache
+- Link to tuning ?
+
+h5. QueryCache
+- Link to tuning ?
+
+h5. JPA 2.0 Caching 
+
+h5. Using MBean performance monitor
+ - ?
+
+h2. Database Connection Pooling
+
+h2. Enhancement 
+
+h2. MetaDataRepository
+
+h2. 
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/powered-by.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/powered-by.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/powered-by.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/powered-by.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,20 @@
+{excerpt:hidden=true}Other products and projects using OpenJPA{excerpt}
+
+This page list products and companies that are currently using OpenJPA.
+
+|!http://www.compass-project.org/images/compassheader3.png!|[Compass|http://www.compass-project.org/] is a first class open source Java Search Engine Framework, enabling the power of Search Engine semantics to your application stack decoratively. Compass has "native" integration with OpenJPA by working in an "embedded" mode within it.|
+|!http://wiki.easybeans.org/xwiki/bin/download/XWiki/MySkin/easybeans.png!|[EasyBeans|http://www.easybeans.net]: EasyBeans is an open source, lightweight and modular EJB3 container hosted by the [OW2 consortium|http://www.ow2.org]. EasyBeans is the EJB container of the [JOnAS application server|http://jonas.objectweb.org]. EasyBeans can be integrated in application servers like [Apache Tomcat|http://tomcat.apache.org] or [Jetty|http://jetty.codehaus.org/jetty/]. There is a version provided as OSGi bundles. Supporting several persistence providers, since the 1.0 RC1 release, OpenJPA is the default persistence provider in some packages.|
+|!http://geronimo.apache.org/images/topleft_logo_437x64.gif!|[Geronimo|http://geronimo.apache.org/]: The Apache Geronimo project is a free Java EE certified application server developed by the Apache Software Foundation and distributed under the Apache license. The goal of the Geronimo project is to produce a server runtime framework that pulls together the best Open Source alternatives to create runtimes that meet the needs of developers and system administrators. OpenJPA 1.0.x is shipped as part of Geronimo 2.0.x through 2.1.3, while OpenJPA 1.2.x is included starting with 2.1.4.|
+|!http://t1d.www-306.cacheibm.com/software/main/img/com/ws_brandmark_title.gif!|[IBM WebSphere Application Server V8.5|http://www.ibm.com/developerworks/downloads/ws/was/] is a Java EE 6 certified application server which includes OpenJPA 2.2.x, allowing users to simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. \\
+[IBM WebSphere Application Server V8.0|http://www.ibm.com/developerworks/downloads/ws/was/] is a Java EE 6 certified application server which includes OpenJPA 2.1.x, allowing users to simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. \\
+[Feature Pack for OSGi Applications and JPA 2.0 for WebSphere Application Server v7.0|http://www-01.ibm.com/software/webservers/appserv/was/featurepacks/osgi/] This OSGi / JPA 2.0 Feature Pack delivers JPA 2.0 functionality (based on OpenJPA 2.0.x) for existing Java EE 5 users on WebSphere Application Server v7.0.\\
+[IBM WebSphere Application Server V7.0|http://www.ibm.com/developerworks/downloads/ws/was/] is a Java EE 5 certified application server which includes OpenJPA 1.2.x, allowing users to simply deploy an enterprise archive, web archive, or EJB-JAR that contains a persistence unit. \\
+[Feature Pack for EJB 3.0 for IBM WebSphere Application Server V6.1|http://www-01.ibm.com/support/docview.wss?rs=177&uid=swg21287579]: The Feature Pack for EJB 3.0 delivers several new Java EE 5 technologies, including EJB 3.0 and Java™ Persistence API (JPA based on OpenJPA 1.0.x), for existing Java EE 1.4 users on WebSphere Application Server V6.1. \\
+[IBM WebSphere Application Server Community Edition V2.1|http://www.ibm.com/developerworks/websphere/zones/was/wasce.html] is a Java EE 5 certified application server based on [Apache Geronimo|http://geronimo.apache.org/], which includes OpenJPA.|
+|!http://james.apache.org/images/logos/james-project-logo.gif!|[James|http://james.apache.org/]: The Apache James Project delivers a rich set of open source modules and libraries, written in Java, related to Internet mail communication which build into an advanced enterprise mail server. OpenJPA is used in one of the mailbox persistence mechanisms.|
+|!http://ode.apache.org/logo.data/ODE_logo_v6-1.png!|[ODE|http://ode.apache.org/]: ODE (Orchestration Director Engine) is an Apache project to develop an open-source, Apache-licensed, implementation of the WS-BPEL specification. ODE is a choreography engine allowing you to develop processes to call services in a well-defined manner. OpenJPA 0.9.7 is included in versions 1.0 and 1.1, OpenJPA 1.1.0 is included in version 1.2, and OpenJPA 1.2.1 is included in version 1.3.|
+|!http://code.google.com/p/openmeetings/logo?cct=1316071860!|[OpenMeetings|http://code.google.com/p/openmeetings/]: OpenMeetings is a free browser-based software that allows you to set up instantly a conference in the Web.|
+|Oracle WebLogic Server|[Oracle WebLogic Server|http://www.oracle.com/us/products/middleware/application-server/index.html]: WebLogic Server 10 uses Kodo as the default JPA implementation, and for various internal services. Kodo, in turn, includes OpenJPA.|
+|!http://incubator.apache.org/syncope/images/apache-syncope-logo-small.jpg!|[Syncope|http://incubator.apache.org/syncope/]: Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in JEE technology and released under Apache 2.0 license.  OpenJPA is managing the persistence layer and allows Syncope to run on a wide variety of DBMS.|
+|!http://openejb.staging.apache.org/images/feather-logo.png!|[TomEE|http://openejb.apache.org/apache-tomee.html]: OpenEJB/TomEE is an open source, modular, configurable, and extendable EJB Container System and EJB Server. OpenJPA is included with OpenEJB version 3.0 and later.|
+|!http://tuscany.apache.org/images/TuscanyLogo.jpg!|[Tuscany|http://tuscany.apache.org/]: Apache Tuscany simplifies the task of developing SOA solutions by providing a comprehensive infrastructure for SOA development and management that is based on Service Component Architecture (SCA) standard.|

Added: openjpa/site/trunk/original.cwiki.content/privacy-policy.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/privacy-policy.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/privacy-policy.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/privacy-policy.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,22 @@
+All materials provided on the Apache OpenJPA website (openjpa.apache.org) is Copyright © 2005-2009, The Apache Software Foundation and Licensed under [ASL 2.0|http://www.apache.org/licenses/LICENSE-2.0].
+
+Privacy Policy - Last Updated:  April 29, 2009
+
+Information about your use of this website is collected using [server access logs|http://people.apache.org/~vgritsenko/stats/] and a tracking cookie.  The collected information consists of the following:
+* The IP address from which you access the website;
+* The type of browser and operating system you use to access our site;
+* The date and time you access our site;
+* The pages you visit; and
+* The addresses of pages from where you followed a link to our site.
+
+Part of this information is gathered using a tracking cookie set by the [Google Analytics|http://www.google.com/analytics/] service and handled by Google as described in their [privacy policy|http://www.google.com/privacy.html]. See your browser documentation for instructions on how to disable the cookie if you prefer not to share this data with Google.
+
+We use the gathered information to help us make our site more useful to visitors and to better understand how and when our site is used. We do not track or collect personally identifiable information or associate gathered data with any personally identifying information from other sources.
+
+By using this website, you consent to the collection of this data in the manner and for the purpose described above.
+
+Occasionally, at our discretion, we may include links to other third party content or services on our website. These third party sites have separate and independent privacy policies and therefore we have no responsibility or liability for the content and activities of these linked sites.
+
+If we make changes to our privacy policy, we will send a notification to our mailing lists <users@openjpa.apache.org> and <dev@openjpa.apache.org> along with updating the "Last Updated" date at the top of this page.
+
+If there are any questions regarding this privacy policy, you can contact us on the following mailing list <private@openjpa.apache.org>.

Added: openjpa/site/trunk/original.cwiki.content/publishing-serp-to-maven-central-repository.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/publishing-serp-to-maven-central-repository.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/publishing-serp-to-maven-central-repository.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/publishing-serp-to-maven-central-repository.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,80 @@
+h1. Publishing Serp to Maven Central Repository
+h2. Serp Project
+Serp is used by OpenJPA for the bytecode enhancement processing.  It is maintained as a [SourceForge project|http://sourceforge.net/projects/serp].  Serp has been a very solid third-party dependent software project.  OpenJPA has had a dependency on Serp v1.13.1 for a long time.  Recently, a problem was discovered ([JIRA OPENJPA-2240|http://issues.apache.org/jira/browse/OPENJPA-2240]) which required an update to Serp.  Eventually, it was determined that this problem was resolved in the 1.14.1 version of Serp.  Unfortunately, the last version of Serp that was published to Maven Central was version 1.13.1.  This page discusses how to get an updated Serp release into the Maven Central repository.
+
+SourceForge Serp:  https://sourceforge.net/projects/serp/
+Serp homepage:  http://serp.sourceforge.net
+Serp sourcecode:  http://serp.cvs.sourceforge.net/serp
+
+
+h2. Maven Instructions
+The easiest way to get the updated artifacts for Serp 1.14.1 into Maven Central was to follow the instructions on this page:  https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository.  You will need a GPG utility and signature (instructions on that page).  You will also need a login for Sonatype's Nexus server (instructions also on that page).
+
+Since this exercise shouldn't be a common occurrence, I just went the manual route and signed each of the artifacts that were built into my local repository:
+{code}
+> gpg -ab serp-1.14.1-javadoc.jar
+> gpg -ab serp-1.14.1.jar
+> gpg -ab serp-1.14.1-sources.jar
+> gpg -ab serp-1.14.1.pom
+{code}
+
+And, then I created a bundle:
+{code}
+> jar -cvf serp-1.14.1-bundle.jar serp-*
+{code}
+
+The bundle contained:
+{code}
+Archive:  serp-1.14.1-bundle.jar
+  Length     Date   Time    Name
+ --------    ----   ----    ----
+        0  09-04-12 15:23   META-INF/
+       62  09-04-12 15:23   META-INF/MANIFEST.MF
+   962397  09-04-12 15:21   serp-1.14.1-javadoc.jar
+      499  09-04-12 15:22   serp-1.14.1-javadoc.jar.asc
+   140576  09-04-12 15:21   serp-1.14.1-sources.jar
+      499  09-04-12 15:21   serp-1.14.1-sources.jar.asc
+   206638  09-04-12 15:21   serp-1.14.1.jar
+      499  09-04-12 15:22   serp-1.14.1.jar.asc
+     5508  09-04-12 15:21   serp-1.14.1.pom
+      499  09-04-12 15:23   serp-1.14.1.pom.asc
+ --------                   -------
+  1317177                   10 files
+{code}
+
+This bundle is what I uploaded to the Sonatype Staging repository as outlined on that [wiki page|https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository].
+
+{note:title="Not documented.."}
+One process point that was not documented on that [wiki page|https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository] was the need for a JIRA to be created against the OSSRH project (Open Source Project Repository Hosting).  This JIRA should include the Central Repository staging URL that is provided after you upload the bundle.  Here's an [example JIRA|https://issues.sonatype.org/browse/OSSRH-4247] that worked for me.  If all else fails, contact Joel Orlina, jorlina@sonatype.com.
+{note}
+
+h2. Serp Code Updates
+In order to create the -javadoc and -sources jar files, I had to make a couple of minor updates to the existing pom file for serp 1.14.1.  I committed these changes to HEAD (1.14.2 snapshot) for future reference:
+{code}
+      <plugin>
+          <artifactId>maven-source-plugin</artifactId>
+          <executions>
+            <execution>
+                <id>attach-sources</id>
+                <goals>
+                    <goal>jar</goal>
+                </goals>
+            </execution>
+         </executions>
+      </plugin>
+      <plugin>
+          <artifactId>maven-javadoc-plugin</artifactId>
+          <executions>
+            <execution>
+                <id>attach-javadoc</id>
+                <goals>
+                    <goal>jar</goal>
+                </goals>
+            </execution>
+         </executions>
+      </plugin>
+{code}
+
+If we continue to require changes to Serp, we may want to do more extensive changes in the maven processing to make it easier to deploy the artifacts.  Several of the deployment locations in the pom.xml no longer exist.  I made a couple of updates, but the permissions don't show up right, so the deployment step is still manual.
+
+Another idea would be to consume Serp into OpenJPA as an Apache sub-project...  That might be the best long-term solution.  But, I will leave that for another day.
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/query-notes.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/query-notes.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/query-notes.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/query-notes.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,18 @@
+name conflict: QueryImpl from JDBC vs. QueryImpl from kernel
+openjpa.kernel.jpql.JPQLParser
+joins are done by SelectImpl
+subselects have some issues especially with non-relationship 
+src/main/jjtree/org/apache/openjpa/kernel/jpql/JPQL.jjt has rules
+all queries always have a "candidate class" 
+openjpa.jdbc.kernel.exps.JDBCExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+openjpa.kernel.exps.InMemoryExpressionFactory implements openjpa.kernel.exps.ExpressionFactory
+can do in memory filtering by downcasting the JPA Query instance and passing it a collection to filter
+can traverse entity parameters via :param.firstname or :param.relationship.deptname
+DBDictionary contains fields that can be customized per database type
+JPQLExpressionBuilder does semantic analysis by walking the syntax tree and generating the semantic tree
+SQLFactoryImpl constructs the SQL for the query
+SQLBuffer is the result of applying DBDictionary rules to the semantic tree
+Can append SQLBuffer to another SQLBuffer for e.g. subselects
+SQLBuffer is almost a StringBuffer
+ResultSetResult will call ResultSet.getInt etc.
+

Added: openjpa/site/trunk/original.cwiki.content/quick-start.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/quick-start.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/quick-start.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/quick-start.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,40 @@
+{excerpt:hidden=true}Getting Started with OpenJPA{excerpt}
+
+h1. Quick Start Guide
+
+We know it can be hard to find the right help sometimes and search engines can be overwhelming, so we will try to put the most commonly asked for topics with some overview and links to more in-depth resources here for you to checkout, before wasting your time searching through our [Documentation] and [Mailing Lists] for help.
+
+
+h2. Runtime Dependencies
+
+To use OpenJPA as a stand-alone Java component or with a lightweight non-Java EE framework, please refer to the following [Build and Runtime Dependencies] page for the supported levels of Java SE.
+
+To use OpenJPA in a Java EE application server, please refer to the following [Integration] page for the known platforms that either include OpenJPA or have been tested with OpenJPA.
+
+
+h2. JPA Examples
+
+OpenJPA provides some simple examples as part of the binary distribution on the [Downloads] page.  The following [Samples] page provides quick start instructions on how to build and run these samples, along with pointers to other JPA samples from the Apache Geronimo project.
+
+
+h2. Enhancing Entities
+
+The JPA spec requires some type of monitoring of Entity objects, but the spec does not define how to implement this monitoring. Some JPA providers auto-generate new subclasses or proxy objects that front the user's Entity objects at *runtime*, while others use byte-code weaving technologies to enhance the actual Entity class objects at *build time*.  OpenJPA supports both [enhancement|Entity Enhancement] methods, but strongly suggests only using the *build time* enhancement.  The following [Entity Enhancement] page includes more details on both enhancement types, along with examples on how to setup *build time* enhancement in ANT, Maven and Eclipse environments.
+
+
+h2. Tools
+
+OpenJPA provides several design-time and runtime tools, to perform such tasks as entity enhancement, schema mapping, generating metamodel classes and to help migrate from other JPA providers.  Please checkout the [Tools] page for more details.
+
+
+h2. FAQ
+
+Some common questions concerning the history, architecture and usage of OpenJPA can be found on the [FAQ] page.
+
+
+h2. Take the Red Pill
+
+If you want to dive into the rabbit-hole (Hey, It's open source!), then checkout the [Found a Bug] page, which covers everything from posting questions to our mailing lists, to getting the source code and building it, and creating bug patches....
+
+\\
+

Added: openjpa/site/trunk/original.cwiki.content/recovering-from-a-vetoed-release.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/recovering-from-a-vetoed-release.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/recovering-from-a-vetoed-release.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/recovering-from-a-vetoed-release.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,15 @@
+h2. Recovering from a bad release or a vetoed release
+
+Recovering from a bad release actually isn't that difficult. You'll have to delete the bad tag in SVN and rollback the version numbers in all of our pom.xml files. 
+
+h3. Delete the tag in svn
+{code:none}
+$ svn del https://svn.apache.org/repos/asf/openjpa/tags/1.2.0 -m "Rollback release"
+{code}
+h3. Rollback version numbers
+If you have perl installed you can do this in a single command for example to rollback from 1.2.1-SNAPSHOT to 1.2.0-SNAPSHOT
+{code:none}
+$ perl -pi -e "s;<version>1.2.1-SNAPSHOT</version>;<version>1.2.0-SNAPSHOT</version>;g" pom.xml */pom.xml */*/pom.xml
+{code}
+
+If you do not have perl installed you can use a similar tool to edit multiple files or edit them all by hand.

Added: openjpa/site/trunk/original.cwiki.content/related-projects.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/related-projects.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/related-projects.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/related-projects.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,6 @@
+{excerpt:hidden=true}Projects related to OpenJPA{excerpt}
+
+ * [JDO|http://db.apache.org/jdo/]
+
+
+{note}TODO: More Links{note}
\ No newline at end of file

Added: openjpa/site/trunk/original.cwiki.content/release-management.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/release-management.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/release-management.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/release-management.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,40 @@
+h1. Release Management
+{children:depth=3}
+
+h2. Where should I put my fix? 
+Fixes should be targeted and committed on trunk first. Any other open releases are fair game, but may require approval from a release manager. 
+
+h2. Regarding Release Managers
+Once a formal release of OpenJPA has been approved, a release manager is assigned. The release manager is often (but not always) the same developer who performed the release. This release manager role is intended to be a long term branch maintainer who looks after the stability of a formal release. 
+
+The release manager(s) is(are) responsible for targeting fixes into a given version of OpenJPA.
+* Release managers may indicate this by targeting a JIRA issue for their branch or may issue a blanket statement that any fix will be accepted. 
+* In general only the release manager(s) should target a JIRA issue for a branch which they support. 
+** An exception to this rule is if the RM has committed changes for their branch and forgot to update the JIRA issue. 
+* Fixes should not be committed without RM approval. These changes may be reverted by the release manager. 
+
+h3. Some general guidelines for release managers
+* Fixes which are committed to an earlier release should also be present "up-stream". Ie a fix for 1.0.x should also appear in 1.2.x. 
+* Issues may not apply to every release, so the previous guideline may not always apply.
+
+h2. Release Managers for active branches.
+The current release managers for the active branches of OpenJPA are :
+|| branch || internal release number || release manager(s)|| Contact Release Manager before committing ||
+| 0.9.7-r547073 | | Srinivasa Segu | Yes |
+| 1.0.x | 1.0.5-SNAPSHOT | Heath Thomann, Donald Woods | Yes |
+| 1.1.x | 1.1.1-SNAPSHOT | Patrick Linskey, Abe White | Yes |
+| 1.2.x | 1.2.3-SNAPSHOT | Heath Thomann, Donald Woods |  Yes | 
+| 1.3.x | 1.3.0-SNAPSHOT | N/A* | No |
+| 2.0.x | 2.0.2-SNAPSHOT | Donald Woods, Heath Thomann | Yes |
+| 2.1.x | 2.1.1-SNAPSHOT | Heath Thomann | Yes |
+| 2.2.x | 2.2.1-SNAPSHOT | Albert Lee | Yes |
+| trunk | 2.3.0-SNAPSHOT | N/A*| No |
+\* There are no formal releases for these branches.
+
+
+h2. Continuous Builds
+
+We are using the Apache Hudson server for continuous builds of several releases.  Please checkout the [Automated Builds] page for more details.
+
+
+

Added: openjpa/site/trunk/original.cwiki.content/release-setup.cwiki
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/original.cwiki.content/release-setup.cwiki?rev=1415738&view=auto
==============================================================================
--- openjpa/site/trunk/original.cwiki.content/release-setup.cwiki (added)
+++ openjpa/site/trunk/original.cwiki.content/release-setup.cwiki Fri Nov 30 16:56:02 2012
@@ -0,0 +1,195 @@
+These setup steps only need to be performed on a particular machine once.
+{info}Developers using Linux workstations can skip over the references to Cygwin.  If using Windows, install cygwin, including *Utils/gnupg* and *Net/openssh* packages.
+{info}
+
+h3. Create and install a SSH key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+# Use ssh-keygen to create an SSH key.
+{note}
+* ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits instead.{note}
+{code:none}
+$ ssh-keygen -t rsa -b 4096
+{code}
+Program defaults should be fine.  No passphrase is required for the ssh key generation.  The keys will be saved in ~/.ssh/id_rsa (private) and ~/.ssh/id_rsa.pub (public).
+{info} See [Authenticating By Public Key (OpenSSH)|http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html] for a good description on why and how to perform this task.
+{info}
+# {{scp}} your SSH public key ~/.ssh/id_rsa.pub created in last step to ~/id_rsa.pub on people.apache.org.
+{code:none} 
+$ cd ~/.ssh
+$ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub 
+$ You will be prompted for your password.
+{code}
+# Use ssh to login to people.apache.org 
+{code:none}
+$ cd ~
+$ ssh <your userid>@people.apache.org
+{code}
+At this point, you will still be prompted for your password.
+# Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.
+{code:none}
+$ mkdir ~/.ssh
+$ chmod 700 ~/.ssh
+{code}
+# Move or append ~/id_rsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.
+{code:none}
+$ mv ~/id_rsa.pub ~/.ssh/authorized_keys
+or
+$ cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+$ chmod 600 ~/.ssh/authorized_keys
+{code}
+{info}
+* Each public key in the {{authorized_keys}} spans only one line.
+** For example: "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA== dsa-key-20071107}}"
+* '#' in the first column is a comment line.
+{info}
+# Exit out of this ssh session.
+# Start a new ssh session.  No login should be required this time due to the private ssh key on your local box matching up with the public ssh key in your home directory (~/.ssh).
+{code:none}
+$ ssh <your userid>@people.apache.org
+{code} 
+{info}
+If you are still prompted for a password, then you have not set up the ssh keys properly.  Review the steps above and ensure that all of the steps were followed properly.  Or, maybe the instructions are still not quite right and they still need some adjusting.  In that case, please update the instructions accordingly.  :-)
+{info}
+
+
+h3. Create a GPG key
+
+# Open a shell window.  If using Windows, open a cygwin window.
+{info}
+* The generated keys are stored in:
+** *nix - $HOME/.gnupg
+** Windows XP - %HOME%\Application Data\gnupg
+** Windows 7 - C:\ProgramData\GNU\etc\gnupg
+* "gpg --version" shows the GnuPG's home location.
+* Follow the latest steps and guides on the ASF website at [http://www.apache.org/dev/openpgp.html#generate-key] as you need to disable using SHA1 and new keys should be 4096 bits. Append the following text to gpg.conf.
+{code:none}
+personal-digest-preferences SHA512
+cert-digest-algo SHA512
+default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+{code}
+** If you are using an existing gpg certificate, update your current certificate with the above preference using:
+{code:none}
+leealber@jpadev:~/.gnupg$ gpg --edit-key Albert Lee
+Secret key is available.
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Invalid command  (try "help")
+
+Command> showpref
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+
+Command> setpref SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed
+Set preference list to:
+     Cipher: AES256, AES192, AES, CAST5, 3DES
+     Digest: SHA512, SHA384, SHA256, SHA224, SHA1
+     Compression: ZLIB, BZIP2, ZIP, Uncompressed
+     Features: MDC, Keyserver no-modify
+Really update the preferences? (y/N) y
+
+pub  1024D/8007117F  created: 2007-11-05  expires: never       usage: SC  
+                     trust: ultimate      validity: ultimate
+sub  2048g/8D910F8A  created: 2007-11-05  expires: never       usage: E   
+[ultimate] (1). Albert Lee (CODE SIGNING KEY) <allee8285@apache.org>
+
+Command>{code}
+{info}
+# Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).
+{code:none}
+$ gpg --gen-key
+{code}
+The program's default values should be fine.  For the "Real Name" enter your full name (ie. Stan Programmer).  For the "e-mail address" enter your apache address (ie. sprogrammer@apache.org).  You will also be required to enter a "passphrase" for the GPG key generation.  Keep track of this as you will need this for the Release processing.
+{info}
+* Save the content in this subdirectory to a safe media. This contains your private key used to sign all the release materials.
+{info}
+# Backup your cygwin home directory to another media
+# Append your public key to {{[https://svn.apache.org/repos/asf/openjpa/KEYS]}} and {{http://www.apache.org/dist/openjpa/KEYS}}. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the releases. 
+{code:none}
+$ ( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+{code}
+{info}
+* The {{[https://svn.apache.org/repos/asf/openjpa/KEYS]}} file is updated via normal svn commit procedures.
+{code}
+svn co https://svn.apache.org/repos/asf/openjpa --depth empty
+cd openjpa
+svn up KEYS
+( gpg --list-sigs <Real Name> && gpg --armor --export <Real Name> ) >> KEYS
+svn commit KEYS --message "update gpg public key for ME."
+{code}
+* The one under www.apache.org/dist/ has to be manually updated. 
+{code}
+scp KEYS yourid@people.apache.org:/www/www.apache.org/dist/openjpa/KEYS
+{code}
+{info}
+# Submit your public key to a key server. E.g. [http://pgp.surfnet.nl:11371/] or [http://pgp.mit.edu/]
+# Following the instructions in [http://people.apache.org/~henkp/trust/] and ask multiple (at least 3) current Apache committers to sign your public key.
+
+h3. Update Maven settings for our servers
+
+# Create a settings.xml under .m2
+| | {code:xml|title=settings.xml|borderStyle=solid}
+<settings xmlns="http://maven.apache.org/POM/4.0.0"
+          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+    <servers>
+       <!-- SCP settings for people.apache.org -->
+       <server>
+          <id>people.apache.org</id>
+          <username>$USERNAME</username>
+          <privateKey>$PATH_TO_PRIVATE_KEY</privateKey>
+          <passphrase>$SSH_PASSPHRASE</passphrase>
+          <directoryPermissions>775</directoryPermissions>
+          <filePermissions>644</filePermissions>
+          <!-- following is only for Windows only
+          <configuration>
+              <sshExecutable>plink</sshExecutable>
+              <scpExecutable>pscp</scpExecutable>
+              <scpArgs>-2Bp</scpArgs>
+              <sshArgs>-2</sshArgs>
+          </configuration>
+          -->
+       </server>
+       <!-- ASF Nexus settings -->
+       <server>
+           <id>apache.snapshots.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+       <server>
+           <id>apache.releases.https</id>
+           <username>$USERNAME</username>
+           <password>$APACHE_LDAP_PWD</password>
+       </server>
+    </servers> 
+    <profiles>
+        <profile>
+            <id>apache-release</id>
+            <properties>
+                <site.deploy.user.name>$USERNAME</site.deploy.user.name>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+        <profile>
+            <id>gpg-passphrase</id>
+            <properties>
+                <gpg.passphrase>$GPG_PASSPHRASE</gpg.passphrase>
+            </properties>
+        </profile>
+    </profiles>
+</settings>
+{code}
+{info}
+* {{$USERNAME}} is the remote username on people.apache.org, not your local userid.
+* {{$PATH_TO_PRIVATE_KEY}} is the path to the private key generated for ssh. E.g. /home/yourLocalUserId/.ssh/id_rsa.  For Windows' cygwin users, you will need to enter the full cygwin path:  /cygdrive/c/cygwin/home/yourLocalUserId/.ssh/id_rsa.
+* {{$SSH_PASSPHRASE}} for the supplied {{$PATH_TO_PRIVATE_KEY}}.  If you don't use this in your settings.xml file, then you will be prompted for it during the Release processing.
+* {{$GPG_PASSPHRASE}} is pass phase for the GPG key.
+* {{$APACHE_LDAP_PWD}} is your Apache LDAP password, which is shared between SVN and password login for  people.apache.org.
+{info}



Mime
View raw message