| CARVIEW |
Navigation Menu
-
-
Notifications
You must be signed in to change notification settings - Fork 9
Java Version Support
UnoJar explicitly supports LTS java versions. Starting with 2.0 (when it arrives) the major version increments of uno-jar will drop support for a prior LTS version and add support for the next LTS version of java. This is presently achieved by creating an MR jar. Versions between the two supported LTS versions are also intended to be supported but are unlikely to be less well tested.
UnoJar \ JDK |
JDK 8 |
JDK 11 |
JDK 17 |
JDK 21 |
JDK 25 |
0.9.x |
🟢 |
â›” |
â›” |
â›” |
â›” |
1.0.x |
â›” |
🟢 |
â›” |
â›” |
â›” |
1.1.x |
🟢 |
🟢 |
â›” |
â›” |
â›” |
2.0.x (unreleased) |
â›” |
🟢 |
🟢 |
? |
? |
3.0.x (future) |
â›” |
â›” |
🟢 |
🟢 |
? |
If/when new LTS versions come out and they haven’t been tested, they will be denoted here with a ? and it is usually the case that most features continue to work. You are encouraged to give it a try and report any issues here on GitHub.
Related to the above intention for versions of java is how we intend to support old and current versions of Uno-Jar. This library is a side-project for which assistance is welcome, but for the moment it is managed in the spare time of a single developer. Thus extensive support and fixes for past versions is not possible. There are thus three "modes" possible for any given version:
-
New Development - This will be the mode for any unreleased version, typically the main branch or the highest numbered branch_#x if a release is imminent.
-
Supported Release - This will be the state of the most recently release highest major version. Effort will be made by the maintainer(s) to address bugs, and add and release minor features that don’t break back compatibility. Only one branch_#x can have this status at a time. New features and bug fixes not associated with java version back compatibility added here must also be added in any "New Development" branches first and then back-ported to this branch.
-
Contributed Support - All branches older than the supported release branch will accept contributions in the form of Pull Requests from forks. The maintainer(s) will be very unlikely to initiate any work on old versions. The PR must pass all existing tests, and add tests for any fixes to bugs. Contributions that are essentially back ports of features from more recent branches are especially welcome as long as backwards compatibility won’t be broken. Review of these PR’s should be brief and to the point prioritizing accepting assistance from contributors over perfection.