Torsten Curdt | 7 Jun 08:44 2006
Picon

[ANNOUNCEMENT] BCEL 5.2 Released

The Byte Code Engineering Library is intended to give users a  
convenient possibility to analyze, create, and manipulate (binary)  
Java class files. After years of inactivity we are happy to finally  
provide the long awaited 5.2 release including bug fixes and small  
improvements.

See the release notes for further information:

  http://jakarta.apache.org/bcel/RELEASE-NOTES.txt

Binary and source distributions are available at:

  http://jakarta.apache.org/site/downloads/downloads_bcel.cgi

Regards

--

Torsten
Attachment (smime.p7s): application/pkcs7-signature, 3368 bytes
Manfred Duchrow (MDCS | 11 Jun 09:08 2006
Picon

Question about code contribution

Hi BCEL developers!

First of all, thank you very much for this very useful library.
Until lately it was absolutly sufficient and without bug in the
area I needed it.

However, I'm developing a tool named Class Dependency Analyzer
(http://www.programmers-friend.org/CDA/) which uses BCEL to read
.class files and extract the relevant dependency information.
With the latest version (V1.6) of my tool I also support Java 5
classes. My tool particularly needs information about the new
annotation, enum and generic types to compute all dependencies.

Therefore I modified (mainly extend) the code of BCEL 5.1.

Now I want to know if you are interested in getting my changes to
put them into the official BCEL? It would be a first step into the
direction of supporting Java 1.5 class files.
If yes, then I will first adapt my changes to the new BCEL 5.2 before 
sending them to you.
I have a detailed log on what changes I did. So it must be feasable
to integrate my code without too much effort.

What do you think about it?

Regards,
	Manfred

============================================
MDCS - Manfred Duchrow Consulting & Software
(Continue reading)

Torsten Curdt | 11 Jun 09:44 2006
Picon

Re: Question about code contribution

> First of all, thank you very much for this very useful library.
> Until lately it was absolutly sufficient and without bug in the
> area I needed it.

Nice to hear :)

> However, I'm developing a tool named Class Dependency Analyzer
> (http://www.programmers-friend.org/CDA/) which uses BCEL to read
> .class files and extract the relevant dependency information.

Sounds familiar :)

http://vafer.org/projects/dependency/howto.html

> With the latest version (V1.6) of my tool I also support Java 5
> classes. My tool particularly needs information about the new
> annotation, enum and generic types to compute all dependencies.
>
> Therefore I modified (mainly extend) the code of BCEL 5.1.
>
> Now I want to know if you are interested in getting my changes to
> put them into the official BCEL? It would be a first step into the
> direction of supporting Java 1.5 class files.
> If yes, then I will first adapt my changes to the new BCEL 5.2 before
> sending them to you.
> I have a detailed log on what changes I did. So it must be feasable
> to integrate my code without too much effort.
>
> What do you think about it?

(Continue reading)

Yogesh Agarwal | 30 Jun 03:04 2006
Picon

Problem while running JCoverage

I am facing a strange problem while running JCoverage for a project. Same
settings seem to have worked for another project where I implemented
JCoverage. The logs says:

jcoverage 1.0.5 copyright (c)2003 jcoverage ltd. http://jcoverage.com/
jcoverage is licensed under the GNU General Public License
jcoverage comes with ABSOLUTELY NO WARRANTY
instrumenting 286 classes
    [instrument] Exception in thread "main" java.lang.NoSuchMethodError
    [instrument]        at
org.apache.bcel.classfile.LineNumberTable.toString(LineNumberTable.java:169)
    [instrument]        at org.apache.bcel.classfile.Code.toString(Code.java
:342)
    [instrument]        at com.jcoverage.util.JavaClassHelper.dump(
JavaClassHelper.java:64)
    [instrument]        at com.jcoverage.coverage.Instrument.instrument(
Instrument.java:140)
    [instrument]        at
com.jcoverage.coverage.Instrument.addInstrumentation(Instrument.java:194)
    [instrument]        at
com.jcoverage.coverage.Instrument.addInstrumentation(Instrument.java:206)
    [instrument]        at
com.jcoverage.coverage.Instrument.addInstrumentation(Instrument.java:223)
    [instrument]        at com.jcoverage.coverage.Instrument.main(
Instrument.java:229)

BUILD FAILED

Any help is appreciated.
(Continue reading)


Gmane