<commit_before>JEXL 3.0 uses Maven 3 as the build tool, and requires Java 6 (or later).

The following goals may be useful:
* mvn clean - clean up
* mvn test - compile and run the unit tests
* mvn site - create the documentation
* mvn package - build the jar
* mvn install - build the jar and install in local maven repository
<commit_msg>Build depends on JavaCC which causes issues for IDEs<commit_after>JEXL 3.0 uses Maven 3 as the build tool, and requires Java 6 (or later).

The following goals may be useful:
* mvn clean - clean up
* mvn test - compile and run the unit tests
* mvn site - create the documentation
* mvn package - build the jar
* mvn install - build the jar and install in local maven repository

Note that the Maven build process uses JavaCC to generate some sources.
These are created under target/generated sources and automatically compiled.
The generated class files are needed to compile some of the ordinary Java source files.
This can cause problems for some IDEs, which will need to be configured accordingly.
 
{'fraction_non_alphanumeric': 0.04226705091258405, 'fraction_numerical': 0.007684918347742555, 'mean_word_length': 3.961904761904762, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6736306', 'n_tokens_mistral': 285, 'n_tokens_neox': 265, 'n_words': 166}