| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
cannot cope with 4000 jars on the classpath. These enhancements cause things to be done 'lazily' in BCEL.
|
| |
|
| |
|
|
|
|
|
|
| |
frequently than we import new versions of BCEL into AspectJ - so it makes sense to make that patching process easier than the importing process. Also the Java5 support would result in an unwieldy patch.txt file.
The ANT targets in build.xml will still enable transformation of the packaging from org.aspectj.apache to org.apache for diffing with a new BCEL version, should one ever appear.
|
| |
|
|
|
|
| |
build.xml to construct a bcel-src.zip that matches the bcel.jar - to ease debugging.
|
|
|
|
|
| |
instigated by Andy actually trying to use
this module the way it is supposed to be used
|
|
|
|
| |
the build process.
|
|
|
|
| |
one file to see if it makes the build happy (we had to do this for adrians new module). If it fails then I'll delete it and wait for George to return who knows the right cruise control incantations to locate the problem.
|
|
|
|
| |
ignore it correctly?
|
|
|
|
| |
LocalVariableTable sometimes gets BCEL-supplied parameter names
|
|
|