king
/
v811_spc009
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'main'
${ noResults }
v811_spc009/external/apache-commons-bcel
History
jianglk.darker 7ee447c011
v811_spc009_project 		4 months ago
..
docs v811_spc009_project 4 months ago
src v811_spc009_project 4 months ago
.travis.yml v811_spc009_project 4 months ago
Android.bp v811_spc009_project 4 months ago
CONTRIBUTING.md v811_spc009_project 4 months ago
LICENSE v811_spc009_project 4 months ago
LICENSE.txt v811_spc009_project 4 months ago
METADATA v811_spc009_project 4 months ago
MODULE_LICENSE_APACHE2 v811_spc009_project 4 months ago
NOTICE.txt v811_spc009_project 4 months ago
OWNERS v811_spc009_project 4 months ago
README.md v811_spc009_project 4 months ago
README.version v811_spc009_project 4 months ago
RELEASE-NOTES.txt v811_spc009_project 4 months ago
TODO.JustIce v811_spc009_project 4 months ago
pom.xml v811_spc009_project 4 months ago

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