Author: helenxu
Date: Wed Nov 21 16:12:15 2012
New Revision: 1412167
URL: http://svn.apache.org/viewvc?rev=1412167&view=rev
Log:
CMS migration
Modified:
openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext
Modified: openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext?rev=1412167&r1=1412166&r2=1412167&view=diff
==============================================================================
--- openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext
(original)
+++ openjpa/site/trunk/content/openjpaeclipseenhancementbuilder.mdtext Wed Nov
21 16:12:15 2012
@@ -12,12 +12,12 @@ Once you have [installed the OpenJPA Ecl
1. 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?)
-1. # choose if OpenJPA libraries should be added to project, this will copy
+ 1. 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.)
-1. # 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)
+ 1. 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)
.
1. menu Project > Properties (or right-click on Project > Properties) should
now show the "OpenJPA PC-Enhancer Project Builder" added after the usual
@@ -45,7 +45,7 @@ log weird error messages in that case
* 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
+\> 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
@@ -74,11 +74,10 @@ something goes wrong with the Progress v
not update correctly anymore, and appear to keep running (although it's
not).
-
- <projectDescription>
- ...
+ <projectDescription>
+ ...
<buildSpec>
- ...
+ ...
<buildCommand>
<name>org.apache.openjpa.eclipse.OpenJPAEnhancerBuilder</name>
<arguments>
@@ -88,20 +87,15 @@ not).
</dictionary>
-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) :
+ 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) :
- 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
+ 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
* The builder has been written with efficiency in mind and underwent some
@@ -116,10 +110,10 @@ Ant-like patterns, by manually adding th
.project file of the Eclipse Java project:
- <projectDescription>
- ...
+ <projectDescription>
+ ...
<buildSpec>
- ...
+ ...
<buildCommand>
<name>org.apache.openjpa.eclipse.OpenJPAEnhancerBuilder</name>
<arguments>
@@ -133,5 +127,4 @@ Ant-like patterns, by manually adding th
</dictionary>
-* The above two options can be mixed by adding several <dictionary> inside
-the <arguments>.
+* The above two options can be mixed by adding several `<dictionary>` inside
the `<arguments>`.
