Apache Commons Lang
Go to file
Benedikt Ritter 09043bfa6f
Update version numbers for release 3.6
2017-06-09 11:38:15 +02:00
src Update website for 3.6 release 2017-06-09 11:38:15 +02: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 Add FindBugs to Travis CI (closes #262) 2017-04-19 18:25:04 +02: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 Update website for 3.6 release 2017-06-09 11:38:15 +02:00
RELEASE-NOTES.txt Update website for 3.6 release 2017-06-09 11:38:15 +02:00
checkstyle-suppressions.xml Prevent redundant modifiers 2017-06-06 16:11:45 +02:00
checkstyle.xml Make sure placement of curly braces is consistent 2017-06-06 22:14:47 +02:00
findbugs-exclude-filter.xml Exclude SF_SWITCH_NO_DEFAULT on FastDatePrinter 2017-04-19 18:24:57 +02:00
pom.xml Update version numbers for release 3.6 2017-06-09 11:38:15 +02:00

README.md

Apache Commons Lang

Build Status Coverage Status Maven Central

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