openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r1415715 - in /openjpa/site/trunk: WhoIsWorkingOnWhat.txt content/getting-started.mdtext content/testing.mdtext content/whither-openjpa.mdtext
Date Fri, 30 Nov 2012 16:01:11 GMT
Author: allee8285
Date: Fri Nov 30 16:01:09 2012
New Revision: 1415715

URL: http://svn.apache.org/viewvc?rev=1415715&view=rev
Log:
CMS migration updates.

Modified:
    openjpa/site/trunk/WhoIsWorkingOnWhat.txt
    openjpa/site/trunk/content/getting-started.mdtext
    openjpa/site/trunk/content/testing.mdtext
    openjpa/site/trunk/content/whither-openjpa.mdtext

Modified: openjpa/site/trunk/WhoIsWorkingOnWhat.txt
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/WhoIsWorkingOnWhat.txt?rev=1415715&r1=1415714&r2=1415715&view=diff
==============================================================================
--- openjpa/site/trunk/WhoIsWorkingOnWhat.txt (original)
+++ openjpa/site/trunk/WhoIsWorkingOnWhat.txt Fri Nov 30 16:01:09 2012
@@ -37,7 +37,7 @@ done			fetch-statistics.mdtext
 done			findbugs-presentation-notes.mdtext
 done			found-a-bug.mdtext
 done			get-involved.mdtext
-helenxu			getting-started.mdtext
+done			getting-started.mdtext
 done			index.mdtext
 delete			index-top-link.mdtext
 done			integration.mdtext
@@ -63,7 +63,7 @@ done			mailing-lists.mdtext
 delete			mdd.mdtext
 done			migration-tool.mdtext
 done			obtaining.mdtext
-done        penbooks---featuring-jpa-2.0.mdtext
+done        	openbooks---featuring-jpa-2.0.mdtext
 done			openjpa-2.0.0-beta-2.mdtext
 done			openjpa-2.0.0-beta-3.mdtext
 done			openjpa-2.0.0-beta.mdtext
@@ -103,8 +103,8 @@ done			recovering-from-a-vetoed-release.
 done			related-projects.mdtext
 done			release-management.mdtext
 done			release-setup.mdtext
-			releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).mdtext
-			releasing-openjpa-1.2.x-(old-scp-steps).mdtext
+save			releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).mdtext
+save			releasing-openjpa-1.2.x-(old-scp-steps).mdtext
 done			running-openjpa-examples.mdtext
 done			running-the-sun-tck-for-jpa.mdtext
 done			runtime-enhancement.mdtext
@@ -118,7 +118,7 @@ done  			sidenav-quick-links.mdtext
 done			site-index.mdtext
 delete			site-map.mdtext
 done			source-code.mdtext
-rgcurtis		testing.mdtext
+done			testing.mdtext
 done			thanks.mdtext
 done			tools.mdtext
 done			top-navigation-bar.mdtext
@@ -126,6 +126,6 @@ done			update-release-text-files.mdtext
 done			using-criteria-api-in-daytrader.mdtext
 done			verifying-release-signatures.mdtext
 done			websphere-application-server.mdtext
-delete?			whither-openjpa.mdtext
-delete?			wiki.mdtext
+done			whither-openjpa.mdtext
+delete			wiki.mdtext
 done			writing-test-cases-for-openjpa.mdtext

Modified: openjpa/site/trunk/content/getting-started.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/getting-started.mdtext?rev=1415715&r1=1415714&r2=1415715&view=diff
==============================================================================
--- openjpa/site/trunk/content/getting-started.mdtext (original)
+++ openjpa/site/trunk/content/getting-started.mdtext Fri Nov 30 16:01:09 2012
@@ -1,12 +1,12 @@
 Title: Getting started
 <a name="Gettingstarted-Notes"></a>
-### Notes
+## Notes
 These instructions detail the steps required to run a give sample for a number of different
environments. You can substitute any of the directories in the \[binary download\](binary-download\.html)
 \examples\ directory for __hellojpa__ in the instructions below to run a
 different sample.
 
 <a name="Gettingstarted-GettingStartedwiththeEclipse"></a>
-### Getting Started with the Eclipse
+## Getting Started with the Eclipse
 
 1. Download the OpenJPA binary release from the [downloads](downloads.html)
  page and unpack it by double-clicking it.
@@ -39,7 +39,7 @@ entity class, play with them by adding f
 persistence operations. Have fun!
 
 <a name="Gettingstarted-GettingStartedwiththeConsole"></a>
-### Getting Started with the Console
+## Getting Started with the Console
 
 1. Ensure that you have [Apache Ant](http://ant.apache.org/)
  installed (this sample was tested with ant 1.6.5, but any recent version
@@ -59,7 +59,7 @@ entity class, play with them by adding f
 persistence operations. Have fun!
 
 <a name="Gettingstarted-GettingStartedwithNetbeans"></a>
-### Getting Started with Netbeans
+## Getting Started with Netbeans
 
 1. Download the OpenJPA binary release from the [downloads](downloads.html)
  page and unpack it by double-clicking it.

Modified: openjpa/site/trunk/content/testing.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/testing.mdtext?rev=1415715&r1=1415714&r2=1415715&view=diff
==============================================================================
--- openjpa/site/trunk/content/testing.mdtext (original)
+++ openjpa/site/trunk/content/testing.mdtext Fri Nov 30 16:01:09 2012
@@ -1,9 +1,7 @@
 Title: Testing
-{excerpt:hidden=true}Running and [Writing](writing-test-cases-for-openjpa.html)
- OpenJPA unit tests{excerpt}
+<a name="Testing"></a>
 
-h1. Running and [Writing](writing-test-cases-for-openjpa.html)
- Tests with OpenJPA
+# Running and [Writing](writing-test-cases-for-openjpa.html) Tests with OpenJPA
 
 OpenJPA's unit tests are written using JUnit. For a template for a simple
 test case, see the code for [TestPersistence.java](http://svn.apache.org/viewvc/openjpa/trunk/openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/simple/TestPersistence.java?view=markup)
@@ -16,13 +14,16 @@ Once you have downloaded and built OpenJ
 ), you can run individual tests using the "test" goal to maven. For
 example:
 
-
+    mvn test -DfailIfNoTests=false -Dtest=TestPersistence
     
-    {note} By default Maven will fail if there are no testcases found in any
+ <table class="note"><tr>
+  <td valign="top"> <IMG src="images/warning.gif" width="16" height="16" border="0">
+  <td>By default Maven will fail if there are no testcases found in any
 module you build. The examples solve this by specifying
 -DfailIfNoTests=false but you can also change your personal default by
-adding the following to $\{user.home\}/.m2/settings.xml : 
-    {code:xml}
+adding the following to ${user.home}/.m2/settings.xml :
+
+ 
     	<profile>
     	    <id>enable-no-tests</id>
     	    <activation>
@@ -32,42 +33,29 @@ adding the following to $\{user.home\}/.
     		<failIfNoTests>false</failIfNoTests>
     	    </properties>
     	</profile>
-
-{note} 
+    	
+ </tr></table>
 
 To get more debugging information (e.g., to see the SQL that is being
 executed against the database), you can enable trace-level logging from the
 command line using the "openjpa.Log" system property. For example:
 
-
-    $ mvn test -DfailIfNoTests=false -Dtest=TestPersistence
--Dopenjpa.Log=DefaultLevel=TRACE
+    $ mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Dopenjpa.Log=DefaultLevel=TRACE
     
-    [INFO]
- Scanning for projects...
-    [INFO]
- Reactor build order: 
+    [INFO] Scanning for projects...
+    [INFO] Reactor build order: 
     ...
-    690  test  TRACE  [main]
- openjpa.jdbc.SQL - <t 4261185, conn 3061987> executing prepstmnt 12659709 
-       INSERT INTO AllFieldTypes (id, arrayOfStrings, booleanField, byteField,
-charField, dateField, 
+    690  test  TRACE  [main] openjpa.jdbc.SQL - <t 4261185, conn 3061987> executing
prepstmnt 12659709 
+       INSERT INTO AllFieldTypes (id, arrayOfStrings, booleanField, byteField, charField,
dateField, 
        doubleField, floatField, intField, longField, shortField, stringField) 
        VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [params=(long) 601, (null) null, (int)
0, (byte) 0, 
        (int) 0, (null) null, (double) 0.0, (float) 0.0, (int) 0, (long) 0, (short) 0, (null)
null]
-    701  test  TRACE  [main]
- openjpa.jdbc.SQL - <t 4261185, conn 3061987> [11 ms]
- spent
-    701  test  TRACE  [main]
- openjpa.jdbc.JDBC - <t 4261185, conn 3061987> [0 ms]
- commit
-    702  test  TRACE  [main]
- openjpa.jdbc.JDBC - <t 4261185, conn 0> [0 ms]
- close
+    701  test  TRACE  [main] openjpa.jdbc.SQL - <t 4261185, conn 3061987> [11 ms] spent
+    701  test  TRACE  [main] openjpa.jdbc.JDBC - <t 4261185, conn 3061987> [0 ms] commit
+    702  test  TRACE  [main] openjpa.jdbc.JDBC - <t 4261185, conn 0> [0 ms] close
     ...
     $
 
-
 <a name="Testing-SettingadditionalLogparameters"></a>
 ## Setting additional Log parameters
 
@@ -101,17 +89,17 @@ output.
 For example, to avoid enhancement warnings, get detailed SQL information,
 and write the log data to a file:
 
-
+    mvn test -Dtest=TestPersistence -Dopenjpa.Log=Enhance=ERROR,SQL=TRACE,file=openjpa.log
     
-    h1. Testing against alternate databases
+# Testing against alternate databases
     
-    By default, OpenJPA uses the [Derby|http://db.apache.org/derby/]
- database for testing. The {{openjpa-persistence-jdbc/pom.xml}} POM
+By default, OpenJPA uses the [Derby](http://db.apache.org/derby/)
+database for testing. The `openjpa-persistence-jdbc/pom.xml` POM
 declares various pre-defined databases against which tests can be executed.
-For example, to test against the stand-alone [HSQLDB|http://hsqldb.org/]
+For example, to test against the stand-alone [HSQLDB](http://hsqldb.org/)
  database, you can run with the "test-hsqldb" profile:
     
-
+    mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Ptest-hsqldb
 
 For databases that are not in the pre-defined list, you can manually
 specify connection parameters to use for testing under the "test-custom"
@@ -130,7 +118,7 @@ might run:
 
 If you frequently need to test against another database, you can
 permanently declare the database connection parameters in the
-*~/.m2/settings.xml* file under a custom profile. For example:
+`~/.m2/settings.xml` file under a custom profile. For example:
 
 
     <settings>
@@ -138,13 +126,10 @@ permanently declare the database connect
     	<profile>
     	    <id>test-oracle</id>
     	    <properties>
-    		<test-custom>true</test-custom>
-    	       
-<openjpa.custom.driverjar>${user.home}/.m2/privaterepos/jdbc-oracle-10_2_0_1_0.jar</openjpa.custom.driverjar>
-    	       
-<openjpa.custom.driverclass>oracle.jdbc.driver.OracleDriver</openjpa.custom.driverclass>
-    	       
-<openjpa.custom.url>jdbc:oracle:thin:@HOST:PORT:DBNAME</openjpa.custom.url>
+    		<test-custom>true</test-custom>    	       
+            <openjpa.custom.driverjar>${user.home}/.m2/privaterepos/jdbc-oracle-10_2_0_1_0.jar</openjpa.custom.driverjar>
+            <openjpa.custom.driverclass>oracle.jdbc.driver.OracleDriver</openjpa.custom.driverclass>
   	       
+            <openjpa.custom.url>jdbc:oracle:thin:@HOST:PORT:DBNAME</openjpa.custom.url>
     		<openjpa.custom.username>USERNAME</openjpa.custom.username>
     		<openjpa.custom.password>PASSWORD</openjpa.custom.password>
     	    </properties>
@@ -155,11 +140,7 @@ permanently declare the database connect
 
 This profile can then be executed by running:
 
-
-    mvn test -DfailIfNoTests=false -Dtest=TestPersistence
--Ptest-custom,test-oracle
-
-
+    mvn test -DfailIfNoTests=false -Dtest=TestPersistence -Ptest-custom,test-oracle
 
 <a name="Testing-RunningJUnitsinEclipse"></a>
 # Running JUnits in Eclipse
@@ -168,37 +149,44 @@ You'll probably want to setup a Debug Co
 the JUnit testcases.
 
 1. Run --> Debug Configurations...  Create a new JUnit configuration
-!eclipse_dbgcfg_1.png|border=1!
+
+    ![eclipse_dbgcfg_1.png](images/eclipse_dbgcfg_1.png)
+
 1. For the Test tab - Give the configuration a Name, select a Project and
 Test class, and you'll probably want to select the "Keep JUnit running..."
 option.
-!eclipse_dbgcfg_2.png|border=1!
+
+    ![eclipse_dbgcfg_2.png](images/eclipse_dbgcfg_2.png)
+
 1. For the Arguments tab - Press the Variables... button. This will allow us
 to define variables that can be shared across other Release/Debug
 Configurations within this workspace.
-!eclipse_dbgcfg_3.png|border=1!
+
+    ![eclipse_dbgcfg_3.png](images/eclipse_dbgcfg_3.png)
+
 1. For the Select Variable window - Press the Edit Variables... button.
-!eclipse_dbgcfg_4.png|border=1!
+
+    ![eclipse_dbgcfg_4.png](images/eclipse_dbgcfg_4.png)
+
 1. For the Preferences windows - Press New... to add two variables.
-!eclipse_dbgcfg_5.png|border=1!
+    ![eclipse_dbgcfg_5.png](images/eclipse_dbgcfg_5.png)
 
-    Name = openjpa.trace
-    Value = -Dopenjpa.Log=DefaultLevel=TRACE
-    Description = Set OpenJPA logging to TRACE
+        Name = openjpa.trace
+        Value = -Dopenjpa.Log=DefaultLevel=TRACE
+        Description = Set OpenJPA logging to TRACE
 
-!eclipse_dbgcfg_6.png|border=1!
+    ![eclipse_dbgcfg_6.png](images/eclipse_dbgcfg_6.png)
 
-    Name = connect.derby
-    Value = -Dopenjpa.ConnectionDriverName=org.apache.derby.jdbc.EmbeddedDriver
--Dopenjpa.ConnectionURL=jdbc:derby:target/database/openjpa-derby-database;create=true
-    Description = Connection properties for Derby
+        Name = connect.derby
+        Value = -Dopenjpa.ConnectionDriverName=org.apache.derby.jdbc.EmbeddedDriver
+            -Dopenjpa.ConnectionURL=jdbc:derby:target/database/openjpa-derby-database;create=true
+        Description = Connection properties for Derby
 
-!eclipse_dbgcfg_7.png|border=1!
-1. After the above are created and saved, add the new variables as VM
-Arguments.
+    ![eclipse_dbgcfg_7.png](images/eclipse_dbgcfg_7.png)
 
-    ${openjpa.trace}
-    ${connect.derby}
+1. After the above are created and saved, add the new variables as VM Arguments.
 
-!eclipse_dbgcfg_8.png|border=1!
+        ${openjpa.trace}
+        ${connect.derby}
 
+    ![eclipse_dbgcfg_8.png](images/eclipse_dbgcfg_8.png)

Modified: openjpa/site/trunk/content/whither-openjpa.mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/whither-openjpa.mdtext?rev=1415715&r1=1415714&r2=1415715&view=diff
==============================================================================
--- openjpa/site/trunk/content/whither-openjpa.mdtext (original)
+++ openjpa/site/trunk/content/whither-openjpa.mdtext Fri Nov 30 16:01:09 2012
@@ -1,27 +1,33 @@
 Title: Whither OpenJPA
+<a name="Whither-OpenJPA"></a>
+
 Discussion topics: OpenJPA 1.0, OpenJPA 1.1, JPA 2.0, SDO, etc.
 
 * JPA 2.0: Any of OpenJPA members on the expert group? 
-Patrick will be on the EG. There will be a lurker list set up by each EG
+
+    Patrick will be on the EG. There will be a lurker list set up by each EG
 member for internal discussions.
 
 * Does Apache want to have representation on the JPA 2.0 EG? There would be
 an advantage for OpenJPA community members who are not privy to an internal
 lurker alias, to be able to participate in the discussion.
-AI: Craig poll the openjpa community to see if they want to participate
+
+    AI: Craig poll the openjpa community to see if they want to participate
 under NDA in the EG under rules established by the Spec Lead. If positive,
 discuss with Apache JCP representative how to do it. We would need a closed
 Apache-JPA mail alias for discussion and an EG representative to forward
 comments to the expert group.
 
 * Roadmap for OpenJPA. It would be nice to have an idea of when releases
-should come out. 
-What about picking a date, for example, August 20 for branching the
+should come out.
+ 
+    What about picking a date, for example, August 20 for branching the
 release. Everyone who wants a bug fixed for the release, do it by then.
 Marc has volunteered to be release manager. He goes on vacation August 31
 so if the release is delayed beyond that point, someone else needs to push
 it. AI Craig propose a release date and strategy to the community.
 
-* What about the next releases? 
-Craig earlier volunteered to start the roadmap discussion.
+* What about the next releases?
+ 
+    Craig earlier volunteered to start the roadmap discussion.
 



Mime
View raw message