Google Git
Sign in
apache / commons-jcs / refs/heads/master
commit44e9f15ad1175aef4debefc8dc3c0d066dfa0789[log] [tgz]
authorGary Gregory <garydgregory@users.noreply.github.com>Wed Nov 20 11:14:59 2024 -0500
committerGitHub <noreply@github.com>Wed Nov 20 11:14:59 2024 -0500
treec58fc0733a191625bc19a8edb5d7536804d24ce6
parentf90f3233115f92174745c845102a5037f9b1f1f1 [diff]
Bump commons-io:commons-io from 2.17.0 to 2.18.0 #312
1 file changed
tree: c58fc0733a191625bc19a8edb5d7536804d24ce6
  1. .github/
  2. auxiliary-builds/
  3. commons-jcs-jcache-openjpa/
  4. commons-jcs3-core/
  5. commons-jcs3-dist/
  6. commons-jcs3-jcache/
  7. commons-jcs3-jcache-extras/
  8. commons-jcs3-jcache-openjpa/
  9. commons-jcs3-jcache-tck/
  10. commons-jcs3-sandbox/
  11. src/
  12. xdocs/
  13. .asf.yaml
  14. .gitignore
  15. BUILDING.txt
  16. checkstyle.xml
  17. CODE_OF_CONDUCT.md
  18. CONTRIBUTING.md
  19. init-git-svn.sh
  20. jcache-fast.sh
  21. LICENSE.txt
  22. maven-eclipse-codestyle.xml
  23. NOTICE.txt
  24. pom.xml
  25. README.md
  26. RELEASE-NOTES.txt
  27. SECURITY.md
README.md

Apache Commons JCS

Java CI Maven Central Javadocs

Apache Commons JCS is a distributed, versatile caching system.

Documentation

More information can be found on the Apache Commons JCS homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons JCS 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-jcs3</artifactId>
  <version>3.1</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.

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 JCS? Then donate back to the ASF to support the development.

Additional Resources