@Randy, what is the preferred way of contributing to the JETT code?

[Aron Gombas]

We implemented a couple of improvements in JETT recently.
For instance, we introduced a new parameter to the forEach tag that allows optionally copying column-width for iterations with copyRight="true". (This always happens in JETT 0.10.0 and this is suprisingly slow, as discussed by multiple users in one of the tickets.)

I though we'd contribute some of these (the generally useful ones) back to the core source code. How should we do that?

If the project were on GitHub, I'd just send one or more pull requests. (As this is 2017, working with patch files does not sound very compelling.)

[Aron Gombas]

Is there any interest from the maintainers to get contributions or other kind of support for JETT?