Byte Code Engineering Library user discussion

Torsten Curdt | 7 Jun 2006 08:44

[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, 2493 bytes

headers

Manfred Duchrow (MDCS | 11 Jun 2006 09:08

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)

headers

Torsten Curdt | 11 Jun 2006 09:44

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)

headers

Yogesh Agarwal | 30 Jun 2006 03:04

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)

Mon	Tue	Wed	Thu	Fri	Sat	Sun

			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30

1	February 2012
1	August 2011
3	July 2011
6	June 2011
1	September 2010
1	August 2010
3	July 2010
4	June 2010
1	January 2010
3	December 2009
4	November 2009
3	October 2009
1	August 2009
6	July 2009
3	June 2009
9	May 2009
4	April 2009
1	March 2009
6	February 2009
1	January 2009
4	December 2008
13	November 2008
6	October 2008
16	June 2008
7	April 2008
2	March 2008
1	February 2008
15	January 2008
9	December 2007
2	November 2007
5	October 2007
1	September 2007
3	August 2007
5	July 2007
3	June 2007
3	May 2007
1	April 2007
8	March 2007
6	February 2007
11	January 2007
3	December 2006
5	November 2006
2	October 2006
20	September 2006
9	August 2006
17	July 2006
4	June 2006
16	May 2006
21	April 2006
9	March 2006
7	February 2006
9	January 2006
16	December 2005
16	November 2005
5	October 2005
7	September 2005
20	August 2005
3	July 2005
16	June 2005
15	May 2005
7	April 2005
3	March 2005
46	February 2005
35	January 2005
15	December 2004
5	November 2004
8	October 2004
1	September 2004
44	August 2004
19	July 2004
13	June 2004
14	May 2004
15	April 2004
7	March 2004
56	February 2004
25	January 2004
5	December 2003
5	November 2003
8	October 2003
29	September 2003
23	August 2003
12	July 2003
22	June 2003
30	May 2003
52	April 2003
34	March 2003
21	February 2003
37	January 2003
2	December 2002
23	November 2002
51	October 2002
25	September 2002
19	August 2002
2	July 2002
11	June 2002
34	May 2002
24	April 2002
4	March 2002