Google Git
Sign in
android / platform / external / apache-commons-bcel

Bug: 111545888

Clone this repo:

Branches

More...

Tags

More...
  1. 54f0e2b Add janitors to the OWNERS file am: d451b6389c by Sadaf Ebrahimi · 4 months ago main master
  2. d451b63 Add janitors to the OWNERS file by Sadaf Ebrahimi · 4 months ago
  3. 0c56280 Upgrade apache-commons-bcel to BCEL-6.3 am: 72f6971b32 am: 47d72fb5a1 by Sorin Basca · 11 months ago android15-qpr2-release android15-qpr2-s1-release android15-qpr2-s2-release android15-qpr2-s3-release android15-qpr2-s4-release android15-qpr2-s5-release android15-qpr2-s6-release android15-tests-dev android-15.0.0_r20 android-15.0.0_r21 android-15.0.0_r22 android-15.0.0_r23 android-15.0.0_r26 android-15.0.0_r27 android-15.0.0_r28 android-15.0.0_r29 android-15.0.0_r30
  4. 47d72fb Upgrade apache-commons-bcel to BCEL-6.3 am: 72f6971b32 by Sorin Basca · 11 months ago
  5. 72f6971 Upgrade apache-commons-bcel to BCEL-6.3 by Sorin Basca · 11 months ago

Apache Commons BCEL

Build Status Coverage Status Maven Central Javadocs

Apache Commons Bytecode Engineering Library

Documentation

More information can be found on the Apache Commons BCEL homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons BCEL should be posted to the user mailing list.

Where can I get the latest release?

You can download source and binaries from our download page.

Alternatively you can pull it from the central Maven repositories:

<dependency>
  <groupId>org.apache.bcel</groupId>
  <artifactId>bcel</artifactId>
  <version>6.3</version>
</dependency>

Contributing

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:

  • No tabs! Please use spaces for indentation.
  • Respect the code style.
  • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
  • Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running mvn clean test.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement. You can learn more about contributing via GitHub in our contribution guidelines.

License

This code is under the Apache Licence v2.

See the NOTICE.txt file for required notices and attributions.

Donations

You like Apache Commons BCEL? Then donate back to the ASF to support the development.

Additional Resources