Google Git
Sign in
apache / commons-jci / d572775cf0c68d6c3387c9ad30c92b14331e948f
commitd572775cf0c68d6c3387c9ad30c92b14331e948f[log] [tgz]
authorGary Gregory <garydgregory@gmail.com>Wed May 24 13:30:23 2023 -0400
committerGary Gregory <garydgregory@gmail.com>Wed May 24 13:30:23 2023 -0400
tree3bde22a460e8675b4ec3b0f80f456abc8ec7a149
parent5eaf1a856a89622b3b0663e44e0084b9d64478e6 [diff]
Grammar
1 file changed
tree: 3bde22a460e8675b4ec3b0f80f456abc8ec7a149
  1. .github/
  2. compilers/
  3. core/
  4. examples/
  5. fam/
  6. src/
  7. .asf.yaml
  8. .gitignore
  9. CODE_OF_CONDUCT.md
  10. LICENSE.txt
  11. NOTICE.txt
  12. pom.xml
  13. README.md
  14. README.txt
  15. RELEASE-NOTES.txt
  16. SECURITY.md
  17. TODO.txt
README.md

Apache Commons JCI

Travis-CI Status GitHub Actions Status Coverage Status Maven Central Javadocs

Apache Commons JCI is a java compiler interface. It can be used to compile Java itself, or any other language that can be compiled to Java classes (e.g. groovy or javascript). It is well integrated with a FAM (FilesystemAlterationMonitor) that can be used with the JCI compiling/reloading classloader. All the currently supported compilers feature in-memory compilation.

Documentation

More information can be found on the Apache Commons JCI homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons JCI 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-jci2</artifactId>
  <version>2.0</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 JCI? Then donate back to the ASF to support the development.

Additional Resources