Upstream software project

bcel

Javadoc for bcel

About bcel

Javadoc for bcel

This project links 6 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.bcel: recorded package coverageFedora 431 recordsFedora 441 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
bcel
Publisher
Not authoritatively mapped
Native package records
6
Operating systems
fedora-43, fedora-44, opensuse-leap-16-0, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The Byte Code Engineering Library is intended to give users a convenient way to analyze, create, and manipulate (binary) Java class files (those ending with .class). Classes are represented by objects that contain all the symbolic information of the given class: methods, fields, and byte code instructions, in particular. Such objects can be read from an existing file, transformed by a program (such as a class loader at runtime), and dumped to a file again. An even more interesting application is the creation of classes from scratch at runtime. The Byte Code Engineering Library (BCEL) may also be useful if you want to learn about the Java Virtual Machine (JVM) and the format of Java .class files. BCEL is already being used successfully in several projects, such as compilers, optimizers, obfuscators, code generators, and analysis tools. It contains a byte code verifier named JustIce, which usually gives you much better information about what is wrong with your code than the standard JVM message.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package bcel

    43 (Fedora 43) (Unspecified): Byte Code Engineering Library

    6.10.0-4.fc43: noarch

    Source: bcel

Fedora 44

  1. Package bcel

    44 (Fedora 44) (Unspecified): Byte Code Engineering Library

    6.10.0-6.fc44: noarch

    Source: bcel

openSUSE Leap 16.0

  1. Package bcel

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/Java): Byte Code Engineering Library

    6.10.0-160000.2.2: noarch

    Source: bcel

  2. Package bcel-javadoc

    leap-16.0 (openSUSE Leap 16.0) (Documentation/HTML): Javadoc for bcel

    6.10.0-160000.2.2: noarch

    Source: bcel

openSUSE Tumbleweed

  1. Package bcel

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/Java): Byte Code Engineering Library

    6.10.0-1.7: noarch

    Source: bcel

  2. Package bcel-javadoc

    tumbleweed (openSUSE Tumbleweed) (Documentation/HTML): Javadoc for bcel

    6.10.0-1.7: noarch

    Source: bcel

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.