From cdfb3edaeecc171e912040fc9c68fe002bfa459d Mon Sep 17 00:00:00 2001
From: ehilsdal
Date: Fri, 21 May 2004 06:19:07 +0000
Subject: Hopefully better bcel-builder build system, instigated by Andy
actually trying to use this module the way it is supposed to be used
---
bcel-builder/build.xml | 80 +++++++++++++++++++++++++++---------------------
bcel-builder/readme.html | 52 ++++++++++++++++++-------------
2 files changed, 76 insertions(+), 56 deletions(-)
diff --git a/bcel-builder/build.xml b/bcel-builder/build.xml
index 0310d4c3f..98aebeeb8 100644
--- a/bcel-builder/build.xml
+++ b/bcel-builder/build.xml
@@ -1,60 +1,70 @@
-
+
-
+
+
-
+
+
+
-
-
+
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
-
-
-
+
+
+
+
+
+
+
+
+
-
+
-
+
+
+
+
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/bcel-builder/readme.html b/bcel-builder/readme.html
index b5a4c52c8..a0d20b60a 100644
--- a/bcel-builder/readme.html
+++ b/bcel-builder/readme.html
@@ -19,6 +19,9 @@
this directory? Well, the whole point is to generate bcel/bcel.jar in
the lib package. To do so, first stick
bcel-5.1-src.zip in this directory, then run ant.
+(at one point, this was available at
+
+http://archive.apache.org/dist/jakarta/bcel/source/bcel-5.1-src.zip)
After much unzipping, patching, and compiling, you should get an
appropriate bcel.jar file. Now put it in the appropriate place.
@@ -28,28 +31,35 @@ to know some more ant targets. But before anything, get that
bcel-5.1-src.zip and stick it in this directory.
+ There are five top-level ant targets apart from the usual "clean":
+
- - ant unpack -- unpack the sources for the AspectJ-version of BCEL
- into the src subdirectory. Though you probably
- don't care, this invokes the following subtasks:
-
-
- - ant extract -- extract the contents of bcel-5.1-src.zip
- into the bcel-5.1 directory.
-
- - ant patch -- apply the patchfile patch.txt to the
- bcel-5.1/src directory, creating
- src.
-
-
- - ant pack -- pack the sources for AspectJ's version of bcel back
- into a tiny little patchfile. This uses exec, and requires that you
- have diff somewhere on your path. Actually, it's much worse: it
- requires you have diff.exe somewhere on your path. I hate that I'm
- turning into a windows whore.
-
- - ant clean -- get rid of everything extraneous in preparation for
- a checkin.
+ - ant extractAndJar -- this is just the composition of the extract
+ and jar targets, and is the default. It extracts the source from bcel-5.1-src.zip,
+ patches it, compiles the patched version into a jar and drops the new jar,
+ bcel.jar, into the project root. This is the default task, mainly used
+ to sanity check the building and make sure we're generating something.
+ The bcel.jar this generates should be the same as that in ..\lib\bcel\bcel.jar.
+
+
+ - ant extract -- this extracts the source from bcel-5.1-src.zip,
+ patches it, and copies the patched source into the project src directory,
+ there to be visible by eclipse for people to do development on it.
+
+
+ - ant jar -- this copies the edited source from the project source
+ directory and jars it up into bcel.jar, there to be tested.
+
+
+ - ant push -- this pushes the new bcel.jar into ..\lib\bcel\bcel.jar,
+ ready to be used by the greater compiler.
+
+ - ant diff -- this creates the patch.txt file, composed of the differences
+ between the project src directory and the original bcel-5.1 source.
+ All of the tasks are destructive, so don't do "ant extract", for example,
+if you have anything in the project source directory you care about.
+
+