Binary jar archive: yeti.jar (occasionally updated and built from development snapshots)
Binary jar containing only Yeti standard library: yeti-lib.jar

04/2024. Version 1.1 released (yeti-1.1.jar and yeti-lib-1.1.jar).

08/2020. Version 1.0 released (yeti-1.0.jar and yeti-lib-1.0.jar).

10/2015. Version released (yeti- and yeti-lib-

11/2013. Version 0.9.9 released (yeti-0.9.9.jar and yeti-lib-0.9.9.jar).

04/2013. Version 0.9.8 released (yeti-0.9.8.jar and yeti-lib-0.9.8.jar).

11/2012. Version 0.9.7 released (yeti-0.9.7.jar and yeti-lib-0.9.7.jar).

7/2012. Version 0.9.6 released (yeti-0.9.6.jar and yeti-lib-0.9.6.jar).

4/2012. Version 0.9.5 bugfix release (yeti-0.9.5.jar and yeti-lib-0.9.5.jar).

2/2012. Version 0.9.4 released (yeti-0.9.4.jar and yeti-lib-0.9.4.jar).

12/2011. Version 0.9.3 bugfix release (yeti-0.9.3.jar and yeti-lib-0.9.3.jar).

11/2011. Version 0.9.2 released (yeti-0.9.2.jar and yeti-lib-0.9.2.jar).

9/2011. Version 0.9.1 bugfix release (yeti-0.9.1.jar and yeti-lib-0.9.1.jar).

8/2011. Version 0.9 released (yeti-0.9.jar and yeti-lib-0.9.jar).

You should probably still use the development snapshots to get latest bug fixes, unless you need that nothing changes. Main changes and bugfixes since last update:

4/2011. Bunch of bugfixes and some new features:

4/2010. Bugfixes, like always. New features:

Better type mismatch error messages and documentation generation from comments are partially implemented (means doesn’t work yet).

8/2009. Bugfixes, case pattern matching should work now better. Mixed Java/Yeti build task enchasements.

5/2009. Some bugfixes, allowed partial variant match in case, recursive type definitions.

12/2008. Some bugfixes and .[] can now be used for accessing Java array elements too. Also added some smart auto-casting for Java arrays.

10/2008. Java class definitions are supported now. Additionally bunch of bugfixes and optimisations have been done.

9/2008. Some bugfixes here and there have happened (you can read the git log). Java classes are probably next thing to be implemented (actually the syntax is decided and parser support already exists).