Apache Commons Collections
Go to file
Gary Gregory 81e3a7ec04 Update commons-codec from 1.14 to 1.15. 2020-09-01 13:53:31 -04:00
.github Trigger a GitHub build on pull requests. 2020-08-31 21:23:00 -04:00
src Update commons-codec from 1.14 to 1.15. 2020-09-01 13:53:31 -04:00
.gitignore Initial bloom filter code contribution (#83) 2020-01-24 18:10:46 -05:00
.travis.yml refine travis-ci scripts 2020-08-28 17:45:20 +08:00
CONTRIBUTING.md Prepate for release 4.4. 2019-07-05 13:43:30 -04:00
DEVELOPERS-GUIDE.html Drop Subversion Id keywords. 2019-10-17 17:28:50 -04:00
LICENSE.txt Change to Apache License 2.0 2004-02-18 01:00:08 +00:00
NOTICE.txt Update year in NOTICE.txt and changes.xml 2019->2020 2020-01-09 20:21:17 +13:00
PROPOSAL.html Standardize on American English spelling of 'behavior'. 2020-03-30 10:48:32 -04:00
README.md Use license instead of licence. 2020-05-27 11:03:55 +08:00
RELEASE-NOTES.txt find and fix fixtypo (#88) 2019-10-17 08:40:55 -04:00
pom.xml Update commons-codec from 1.14 to 1.15. 2020-09-01 13:31:54 -04:00

README.md

Apache Commons Collections

Build Status Coverage Status Maven Central Javadocs

The Apache Commons Collections package contains types that extend and augment the Java Collections Framework.

Documentation

More information can be found on the Apache Commons Collections homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons Collections 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.commons</groupId>
  <artifactId>commons-collections4</artifactId>
  <version>4.4</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 License v2.

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

Donations

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

Additional Resources