Colors support for CLI output about jdeploy

[mddanishansari]

I had similar issue, you case might be different but this worked for me. I had Jansi in my JAR file, removing jansi.jar from my executable JAR helped fix it for me.

Also try to update jdeploy's dependency shelljs version to 0.8.4

[andrii-bodnar]

@shannah just a friendly reminder 🙂

[ravn]

@andrii-bodnar It is your application that behaves differently, which is most likely due to the ANSI library you use not detecting correctly it is being launched from JDeploy.

What ANSI library do you use and how can you configure it to think it is ok in this situation? Environment variables are typically used for this.

[andrii-bodnar]

@ravn I am using the Picocli tool for building CLI and it's using some ANSI library under the hood (PicocliRunner.java#L61), but I'm not sure what the library is used here.

[ravn]

@andrii-bodnar I had a quick look at the documentation and it looks like the "Enable ANSI or not?" mechanism is described at https://picocli.info/#_heuristics_for_enabling_ansi.

My guess would be that the two environments behave differently regarding either

4. ANSI is enabled when system property os.name starts with "Windows" and JAnsi Console is installed.

or

7. ANSI is disabled when Picocli guesses the program’s output stream is not connected to a terminal: when System.console() returns null. This check is omitted if picocli guesses the program is running in a Windows Cygwin, MSYS or MSYS2 environment: when system property os.name starts with "Windows" and either environment variable TERM contains cygwin or starts with xterm or environment variable OSTYPE is defined.

This will require you to experiment to find out exactly what is different, possibly in a debugger. Please update this issue with your findings.

[andrii-bodnar]

@ravn thanks a lot for the detailed investigation!