Google Git
Sign in
android / platform / external / apache-commons-bcel / febc3d3ef60b8d7fc4a3b8494d86180abc11428b
commitfebc3d3ef60b8d7fc4a3b8494d86180abc11428b[log] [tgz]
authorXin Li <delphij@google.com>Mon Feb 25 00:27:40 2019 -0800
committerXin Li <delphij@google.com>Mon Feb 25 00:27:40 2019 -0800
tree06828ccfd7bfb44c3cf9ba61d0682ef0ee4f198d
parenta7f063ecb35325378d210bdd38e0f6c04ffffac1 [diff]
parent015d868caef22f9a0b7eec58695dd7893f84eb8a [diff]
Merge stage-aosp-master into pi-dev-plus-aosp

Bug: 126125118
Change-Id: Ic76eb82df254f2da952a86828bf7785c1b6430ab
tree: 06828ccfd7bfb44c3cf9ba61d0682ef0ee4f198d
  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
  12. NOTICE.txt
  13. OWNERS
  14. pom.xml
  15. README.md
  16. README.version
  17. RELEASE-NOTES.txt
  18. 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