Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Timeline for next published release #7

Closed
zachbr opened this issue Jun 30, 2019 · 4 comments
Closed

Timeline for next published release #7

zachbr opened this issue Jun 30, 2019 · 4 comments
Labels

Comments

@zachbr
Copy link

zachbr commented Jun 30, 2019

An issue was fixed in a newer version of JLine than is included in the 1.1.1 TCA release.
It looks like master includes a version of JLine with the relevant bug fix. Is there any timeline or known blockers for the next release?

I'd be happy to help you test if that's a concern. Thanks, and thanks for TCA 👍

@stephan-gh
Copy link
Member

I was hoping for jline/jline3#401
At the moment, it makes using Log4j's own %highlight really ugly (empty line after each message). Only TCA's own %highlightError{} has a workaround for this.

@stephan-gh
Copy link
Member

In general, you can update JLine independently from TCA. Just override these two dependencies:

compile("org.jline:jline-reader:3.11.0")
runtime("org.jline:jline-terminal-jna:3.11.0")

It should usually work just fine with newer JLine versions. The JLine version used by TCA only represents the recommended version it was tested with.

@zachbr
Copy link
Author

zachbr commented Jul 1, 2019

Thanks for the prompt responses, I'll take a look at that soon 👍

@stephan-gh
Copy link
Member

My PR was just merged and JLine 1.12.0 was released. I have updated TCA to use the new release.
For now, using the new JLine release is blocked by jline/jline3#411, however.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants