Peter Morgan wrote:
Hi,

We have released a GPL Java Code Coverage tool, called: jcoverage.
Available from, http://jcoverage.com. Why is this of interest to the
subscribers of bcel-user? jcoverage is written using the BCEL library,
it is GPL software, and could be an interesting example for BCEL users
to study.

Its a neat idea, but GPL mixed with BCEL makes me shiver. If you automatically alter my compiled code, does that mean I have to release my code using GPL?

If JCoverage is using BCEL, does that pose a problem for BCEL?

What about at the very least using LGPL? It is far lest strict.


We use BCEL to insert instrumentation into every instruction that has an associated line number. We also record the position of conditional branches so that we can determine branch coverage.

Our GPL source code is available from:
http://jcoverage.com/download/jcoverage.html. You can browse our source
repository via http://jcoverage.bkbits.net/. We welcome, comments and/or
contributions.

jcoverage is also available under a commercial license for the
instrumentation of non-GPL applications.

Regards,
Peter.





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to