Author: britter
Date: Tue Jun 7 18:41:39 2016
New Revision: 1747293
URL: http://svn.apache.org/viewvc?rev=1747293&view=rev
Log:
Finalize package rename by fixing documentation
Modified:
commons/proper/bcel/trunk/README.txt
commons/proper/bcel/trunk/pom.xml
commons/proper/bcel/trunk/src/site/xdoc/faq.xml
commons/proper/bcel/trunk/src/site/xdoc/manual.xml
Modified: commons/proper/bcel/trunk/README.txt
URL:
http://svn.apache.org/viewvc/commons/proper/bcel/trunk/README.txt?rev=1747293&r1=1747292&r2=1747293&view=diff
==============================================================================
--- commons/proper/bcel/trunk/README.txt (original)
+++ commons/proper/bcel/trunk/README.txt Tue Jun 7 18:41:39 2016
@@ -1,12 +1,12 @@
Running a console based verifier
- java org.apache.commons.bcel6.verifier.Verifier fully.qualified.class.Name
+ java org.apache.bcel.verifier.Verifier fully.qualified.class.Name
lets JustIce work standalone.
If you get a "java.lang.OutOfMemoryError", you should increase the
maximum Java heap space. A command like
- java -Xmx1887436800 org.apache.commons.bcel6.verifier.Verifier f.q.c.Name
+ java -Xmx1887436800 org.apache.bcel.verifier.Verifier f.q.c.Name
will usually resolve the problem. The value above is suitable for
big server machines; if your machine starts swapping to disk, try
@@ -18,7 +18,7 @@ Running a graphics based verifier
If you prefer a graphical application, you should use a command like
- java org.apache.commons.bcel6.verifier.GraphicalVerifier
+ java org.apache.bcel.verifier.GraphicalVerifier
to launch one. Again, you may have to resolve a memory issue depending
on the classes to verify.
Modified: commons/proper/bcel/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/commons/proper/bcel/trunk/pom.xml?rev=1747293&r1=1747292&r2=1747293&view=diff
==============================================================================
--- commons/proper/bcel/trunk/pom.xml (original)
+++ commons/proper/bcel/trunk/pom.xml Tue Jun 7 18:41:39 2016
@@ -48,7 +48,7 @@
<commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-bcel</commons.scmPubUrl>
<!-- Configuration properties for the OSGi maven-bundle-plugin -->
<commons.osgi.symbolicName>org.apache.${commons.componentid}</commons.osgi.symbolicName>
-
<commons.osgi.export>org.apache.commons.bcel6.*;version=${project.version};-noimport:=true</commons.osgi.export>
+
<commons.osgi.export>org.apache.bcel.*;version=${project.version};-noimport:=true</commons.osgi.export>
<commons.osgi.import>*</commons.osgi.import>
<commons.osgi.dynamicImport />
<commons.osgi.private />
Modified: commons/proper/bcel/trunk/src/site/xdoc/faq.xml
URL:
http://svn.apache.org/viewvc/commons/proper/bcel/trunk/src/site/xdoc/faq.xml?rev=1747293&r1=1747292&r2=1747293&view=diff
==============================================================================
--- commons/proper/bcel/trunk/src/site/xdoc/faq.xml (original)
+++ commons/proper/bcel/trunk/src/site/xdoc/faq.xml Tue Jun 7 18:41:39 2016
@@ -31,7 +31,7 @@
<b>Q: </b>How can I ... with BCEL?
<br/>
<b>A: </b>Take a look at
- <tt>org.apache.commons.bcel6.util.BCELifier</tt>, it takes a given class
+ <tt>org.apache.bcel.util.BCELifier</tt>, it takes a given class
and converts it to a BCEL program (in Java, of course). It will
show you how certain code is generated using BCEL.
</p>
@@ -85,7 +85,7 @@
<b>A:</b> Use the JustIce verifier that comes together with BCEL
to get more detailed information:
<pre>
- java org.apache.commons.bcel6.verifier.Verifier <your class></pre>
+ java org.apache.bcel.verifier.Verifier <your class></pre>
</p>
</section>
Modified: commons/proper/bcel/trunk/src/site/xdoc/manual.xml
URL:
http://svn.apache.org/viewvc/commons/proper/bcel/trunk/src/site/xdoc/manual.xml?rev=1747293&r1=1747292&r2=1747293&view=diff
==============================================================================
--- commons/proper/bcel/trunk/src/site/xdoc/manual.xml (original)
+++ commons/proper/bcel/trunk/src/site/xdoc/manual.xml Tue Jun 7 18:41:39 2016
@@ -623,7 +623,7 @@
<p>
The "static" component of the <font
face="helvetica,arial">BCEL</font> API resides in the package
- <tt>org.apache.commons.bcel6.classfile</tt> and closely represents class
+ <tt>org.apache.bcel.classfile</tt> and closely represents class
files. All of the binary components and data structures declared
in the <a
href="http://docs.oracle.com/javase/specs/";>JVM
@@ -751,7 +751,7 @@
<section name="3.3 ClassGen">
<p>
- This part of the API (package <tt>org.apache.commons.bcel6.generic</tt>)
+ This part of the API (package <tt>org.apache.bcel.generic</tt>)
supplies an abstraction level for creating or transforming class
files dynamically. It makes the static constraints of Java class
files like the hard-coded byte code addresses "generic". The
@@ -1095,7 +1095,7 @@
<p>
The <tt>search()</tt> method of class
- <tt>org.apache.commons.bcel6.util.InstructionFinder</tt> gets a regular
+ <tt>org.apache.bcel.util.InstructionFinder</tt> gets a regular
expression and a starting point as arguments and returns an
iterator describing the area of matched instructions. Additional
constraints to the matching area of instructions, which can not be
@@ -1577,10 +1577,10 @@ symbolic type signature encoded with <tt
import java.io.*;
import java.util.Iterator;
-import org.apache.commons.bcel6.classfile.*;
-import org.apache.commons.bcel6.generic.*;
-import org.apache.commons.bcel6.Repository;
-import org.apache.commons.bcel6.util.InstructionFinder;
+import org.apache.bcel.classfile.*;
+import org.apache.bcel.generic.*;
+import org.apache.bcel.Repository;
+import org.apache.bcel.util.InstructionFinder;
public class Peephole {
