Your message dated Mon, 7 Sep 2026 17:43:31 +0100
with message-id
<CANNm6ZwHhgz-vzMzpS5pPBzXV9G+MGG5yLEkXLyf6daNMh=5...@mail.gmail.com>
and subject line Re: Bug#1039607: libjansi-java: causes maven to always output
escape character
has caused the Debian Bug report #1039607,
regarding libjansi-java: causes maven to always output escape character
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1039607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039607
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libjansi-java
Version: 2.4.0-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear maintainer,
I'm running commands that use the `mvn` and capture the output coming from it.
More specifically, I'm catching the version of a Maven project with a command
like the following:
mvn --batch-mode --quiet -DforceStdout help:evaluate
-Dexpression="project.version"
Up until Debian Bullseye, the output from the command above was a single string
with only the version, as intended. For example: "1.0.0-SNAPSHOT".
After upgrading to Debian Bookworm, the `mvn` command now outputs escape
characters, regardless of the flags passed to it.
The example above has now become: "ESC[0m1.0.0-SNAPSHOTESC[0m".
I tested with the upstream Maven package of the same version, and could narrow
down the problem as coming from the libjansi-java jar.
If I downgrade it back to the Debian-packaged version 2.4.0-1, the old
behaviour is restored.
This change seems to have been due to this commit:
https://salsa.debian.org/java-
team/jansi/-/commit/7f186cd4fc22308d7769db8eeeca26b560b81b1a
You can probably reproduce this very simply with the following:
(running `mvn` anywhere should work - it doesn't have to have a Maven project
and the error message is irrelevant to reproduce what we need)
mvn --batch-mode --quiet | less
* With libjansi-java 2.4.0-2, escape characters are seen in the output, like
so:
ESC[0m[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
(...)
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
ESC[0m
(END)
* With libjansi-java 2.4.0-1 (downloaded from snapshot.debian.org), escape
characters are not seen in the output:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
(...)
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
(END)
Thank you and best regards,
Luís Picciochi Oliveira
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-0-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
I'm closing this as the current version of libjansi-java in Debian stable,
2.4.1-2, does not display the reported bug anymore.
On Mon, 7 Sept 2026 at 17:41, Pitxyoki <[email protected]> wrote:
> notfound 1039607 2.4.1-2
>
> On Tue, 27 Jun 2023 at 20:05, Pitxyoki <[email protected]> wrote:
>
>> found 1039607 2.4.0-2
>> notfound 1039607 2.4.0-1
>>
>> On 27/06/2023, Luís Picciochi Oliveira <[email protected]> wrote:
>> > Package: libjansi-java
>> > Version: 2.4.0-1
>> > Severity: normal
>> > X-Debbugs-Cc: [email protected]
>> >
>> > Dear maintainer,
>> >
>> > I'm running commands that use the `mvn` and capture the output coming
>> from
>> > it.
>> >
>> > More specifically, I'm catching the version of a Maven project with a
>> > command
>> > like the following:
>> >
>> > mvn --batch-mode --quiet -DforceStdout help:evaluate
>> > -Dexpression="project.version"
>> >
>> >
>> > Up until Debian Bullseye, the output from the command above was a single
>> > string
>> > with only the version, as intended. For example: "1.0.0-SNAPSHOT".
>> >
>> > After upgrading to Debian Bookworm, the `mvn` command now outputs escape
>> > characters, regardless of the flags passed to it.
>> > The example above has now become: "ESC[0m1.0.0-SNAPSHOTESC[0m".
>> >
>> > I tested with the upstream Maven package of the same version, and could
>> > narrow
>> > down the problem as coming from the libjansi-java jar.
>> >
>> > If I downgrade it back to the Debian-packaged version 2.4.0-1, the old
>> > behaviour is restored.
>> >
>> > This change seems to have been due to this commit:
>> > https://salsa.debian.org/java-
>> > team/jansi/-/commit/7f186cd4fc22308d7769db8eeeca26b560b81b1a
>> >
>> >
>> > You can probably reproduce this very simply with the following:
>> > (running `mvn` anywhere should work - it doesn't have to have a Maven
>> > project
>> > and the error message is irrelevant to reproduce what we need)
>> >
>> > mvn --batch-mode --quiet | less
>> >
>> >
>> > * With libjansi-java 2.4.0-2, escape characters are seen in the output,
>> like
>> > so:
>> >
>> > ESC[0m[INFO] Scanning for projects...
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] BUILD FAILURE
>> > (...)
>> > [ERROR] [Help 1]
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
>> > ESC[0m
>> > (END)
>> >
>> >
>> >
>> > * With libjansi-java 2.4.0-1 (downloaded from snapshot.debian.org),
>> escape
>> > characters are not seen in the output:
>> >
>> > [INFO] Scanning for projects...
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] BUILD FAILURE
>> > (...)
>> > [ERROR] [Help 1]
>> >
>> http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException
>> > (END)
>> >
>> >
>> > Thank you and best regards,
>> > Luís Picciochi Oliveira
>> >
>> >
>> > -- System Information:
>> > Debian Release: 12.0
>> > APT prefers stable-security
>> > APT policy: (500, 'stable-security'), (500, 'stable')
>> > Architecture: amd64 (x86_64)
>> > Foreign Architectures: i386
>> >
>> > Kernel: Linux 6.4.0-0-amd64 (SMP w/12 CPU threads; PREEMPT)
>> > Kernel taint flags: TAINT_WARN
>> > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
>> LANGUAGE not
>> > set
>> > Shell: /bin/sh linked to /usr/bin/dash
>> > Init: systemd (via /run/systemd/system)
>> > LSM: AppArmor: enabled
>> >
>>
>>
>> --
>> Luís Picciochi Oliveira
>> Unimos - Associação Tecnológica
>>
>
>
> --
> Luís Picciochi Oliveira
>
--
Luís Picciochi Oliveira
--- End Message ---
