Apache Commons Lang
Go to file
Gary Gregory 22c3047156 Break up testIdentityToStringStringBuilder into multiple test methods. 2017-11-10 11:47:35 -07:00
src Break up testIdentityToStringStringBuilder into multiple test methods. 2017-11-10 11:47:35 -07:00
.gitattributes Fixed line ending issues once and for all 2016-01-17 20:15:51 +01:00
.gitignore Ignore eclipse-cs generated file 2016-12-22 15:46:08 +00:00
.travis.yml revert LANG-1354; java7 has synthetic fields on Integer, jacoco does not yet work with java9 2017-10-11 08:50:01 -07:00
CONTRIBUTING.md Use README.md and CONTRIBUTING.md generated by commons build plugin 2015-01-02 20:09:51 +00:00
LICENSE.txt Add blank line 2004-02-19 21:23:04 +00:00
NOTICE.txt Update copyright year 2017-04-17 14:13:42 +02:00
README.md Correct link to JavaDoc badge image 2017-09-25 20:30:04 +02:00
RELEASE-NOTES.txt Prepare for releasing 3.7. 2017-11-04 12:03:44 -06:00
checkstyle-suppressions.xml Prevent redundant modifiers 2017-06-06 16:11:45 +02:00
checkstyle.xml make checkstyle config more portable (no maven coupling) 2017-09-09 08:51:49 +02:00
findbugs-exclude-filter.xml Fix typo stateme->statement 2017-09-21 22:48:03 +12:00
pom.xml Update version to 3.8-SNAPSHOT. 2017-11-08 08:49:34 -07:00

README.md

Apache Commons Lang

Build Status Coverage Status Maven Central Javadocs

Apache Commons Lang, a package of Java utility classes for the classes that are in java.lang's hierarchy, or are considered to be so standard as to justify existence in java.lang.

Documentation

More information can be found on the homepage. The JavaDoc can be browsed. Questions related to the usage of Apache Commons Lang 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-lang3</artifactId>
  <version>3.6</version>
</dependency>

Contributing

We accept PRs 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

Code is under the Apache Licence v2.

Donations

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

Additional Resources