Google Git
Sign in
android / platform / external / apache-commons-bcel / refs/tags/android-12.1.0_r17
tage4d22060a2719530d1b4dfb9eea43f465c293a88
taggerThe Android Open Source Project <initial-contribution@android.com>Mon Aug 01 11:15:21 2022 -0700
object54df63affa1e609083900cfa53301920b4631cdc 
Android 12.1.0 release 17
commit54df63affa1e609083900cfa53301920b4631cdc[log] [tgz]
authorBob Badour <bbadour@google.com>Tue Feb 16 22:08:42 2021 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Tue Feb 16 22:08:42 2021 +0000
tree7becac4f172bc523d6803aabc6fc4ab2a4c6c259
parentec317ef1ca18d12d5e56e28d7b0930ff8ce2c946 [diff]
parent55f4c2dc47ba402c60a27b574bb842be57df8287 [diff]
[LSC] Add LOCAL_LICENSE_KINDS to external/apache-commons-bcel am: 565ff9a3aa am: 41d1de7b7f am: 55f4c2dc47

Original change: https://android-review.googlesource.com/c/platform/external/apache-commons-bcel/+/1588665

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: Id20ab949acba178ee9d4b825641324868d1792b2
tree: 7becac4f172bc523d6803aabc6fc4ab2a4c6c259
  1. docs/
  2. src/
  3. .gitignore
  4. .travis.yml
  5. Android.bp
  6. CONTRIBUTING.md
  7. LICENSE
  8. LICENSE.txt
  9. METADATA
  10. MODULE_LICENSE_APACHE2
  11. NOTICE.txt
  12. OWNERS
  13. pom.xml
  14. README.md
  15. README.version
  16. RELEASE-NOTES.txt
  17. TODO.JustIce
README.md

Apache Commons BCEL

Build Status Coverage Status Maven Central License

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.2</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