ta4j

Technical Analysis For Java

Ta4j is an open source Java library for technical analysis. It provides the basic components for creation, evaluation and execution of trading strategies.

Features

• [x] 100% Pure Java - works on any Java Platform version 11 or later
• [x] More than 130 technical indicators (Aroon, ATR, moving averages, parabolic SAR, RSI, etc.)
• [x] A powerful engine for building custom trading strategies
• [x] Utilities to run and compare strategies
• [x] Minimal 3rd party dependencies
• [x] Simple integration
• [x] One more thing: it's MIT licensed

Maven configuration

Ta4j is available on Maven Central. You just have to add the following dependency in your pom.xml file.

<dependency>
  <groupId>org.ta4j</groupId>
  <artifactId>ta4j-core</artifactId>
  <version>0.18</version>
</dependency>

For snapshots, add the following repository to your pom.xml file.

<repository>
    <id>sonatype snapshots</id>
    <url>https://oss.sonatype.org/content/repositories/snapshots</url>
</repository>

The current snapshot version is 0.19-SNAPSHOT from the develop branch.

<dependency>
  <groupId>org.ta4j</groupId>
  <artifactId>ta4j-core</artifactId>
  <version>0.19-SNAPSHOT</version>
</dependency>

You can also download example code from the maven central repository by adding the following dependency to your pom.xml:

<dependency>
  <groupId>org.ta4j</groupId>
  <artifactId>ta4j-examples</artifactId>
  <version>0.18</version>
</dependency>

Getting Help

The wiki is the best place to start learning about ta4j. For more detailed questions, please use the issues tracker.

Contributing to ta4j

Here are some ways for you to contribute to ta4j:

• Take a look at the Roadmap items
• Fork this repository and submit pull requests.
• Take a look at How to contribute

See also: the contribution policy and Code of Conduct

Preparing a release

Maintainers can automate the mundane parts of the release process with scripts/prepare-release.sh. The script coordinates Maven's version bump, updates documentation snippets, rolls the changelog forward, and stages the resulting changes so they are ready to review and commit. The script's functionality is validated by scripts/tests/test_prepare_release.sh.

./scripts/prepare-release.sh

By default the script derives the release version from project.version in the root pom.xml, strips the -SNAPSHOT suffix, and increments the final numeric segment to determine the next development snapshot. You can override either value when cutting special releases:

./scripts/prepare-release.sh --release-version 0.19.1 --next-version 0.20

Run the script from a clean working tree. It stages the updated POM files, documentation, and changelog entries automatically (skipping this step when you pass --dry-run) so you can create the release commit (and follow-up snapshot bump) with confidence.

To preview a release (no file writes) run:

./scripts/prepare-release.sh release --dry-run

Example output of a dry run:

Preparing release:
  Release version: 1.5.0
  Next version:    1.6.0-SNAPSHOT
  Mode:            DRY-RUN (no changes applied)

[DRY-RUN] Would set Maven version to 1.5.0 and update changelog/README.
[DRY-RUN] Snapshot bump to 1.6.0-SNAPSHOT is handled separately by CI workflow.
[DRY-RUN] Would update CHANGELOG.md: move 'Unreleased' to '1.5.0' section.
[DRY-RUN] Would update README.md version references.

release_version=1.5.0
next_version=1.6.0-SNAPSHOT
release_notes_file=release/release-notes.md

Automated releases

The Release workflow (.github/workflows/release.yml) automates version bumps, tagging, and publishing to OSSRH/GitHub. It can be triggered manually from the Actions tab using the optional release_version and next_version inputs. When the inputs are omitted the workflow derives the release number from the root pom.xml and calculates the next snapshot version automatically.

To execute the workflow successfully, configure the following repository secrets:

Grant the workflow permission to push to the protected master branch and to create release/* branches and tags. If branch protections are enforced, make sure "Allow GitHub Actions to bypass branch protections" is enabled for master and that the release/* pattern permits direct pushes from the github-actions[bot] account.

Powered by