public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "KAVALAGIOS Panagiotis (EEAS-EXT)" <Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [cygwin] Re: jansi bug adds spaces to output from maven build using java on w10
Date: Wed, 6 Jan 2021 07:53:59 +0000	[thread overview]
Message-ID: <a62b788116ea47adb39e160d01404216@BELBRU-EXMP101.eeas.europa.eu> (raw)
In-Reply-To: <bef1bdda-0296-ef61-39e5-e2525276a127@SystematicSw.ab.ca>

> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Brian Inglis
> On 2021-01-05 09:15, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> > I would still prefer the Cygwin update though to avoid extra
> > configuration and have it working out-of-the-box :)
> 
> You can update using the snapshots now, or wait (weeks?) until the
> volunteer DLL maintainers have enough updates for a new release and
> enough free time from their real lives, to run tests, build, package, and ship a
> new release, which could cause other issues with other external packages.
> 
> You could also fix the actual problem by updating jansi now.

I know exactly what are my options and believe me, there are more than the one reported here. In my case, we need to update Cygwin Git in our machines, so a solution to stick to 3.0.7 and update only Git is also fine. 

However, we have performed a full update and found the issue with maven in our pilot phase. My interest is not personal for my machine, but to prepare a Cygwin package to push the update to all developers. I need only to know when there will be the new release that will include a fix for this issue as I am not aware of the Cygwin release schedule. Based on the information, we can decide what option fits better our institution.

Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017

  reply	other threads:[~2021-01-06  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 11:59 cygwin introduces spaces in the console output when running a maven build for a java project in windows 10 Valentin Brasov
2020-12-29 13:28 ` Marco Atzeri
2020-12-29 13:38 ` Takashi Yano
2021-01-05 14:46   ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-05 15:48     ` [cygwin] " Jason Pyeron
2021-01-05 16:15       ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-05 16:54         ` [cygwin] Re: jansi bug adds spaces to output from maven build using java on w10 Brian Inglis
2021-01-06  7:53           ` KAVALAGIOS Panagiotis (EEAS-EXT) [this message]
2021-01-06  8:16             ` Brian Inglis
2021-01-06  9:14               ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-06  1:36     ` cygwin introduces spaces in the console output when running a maven build for a java project in windows 10 Takashi Yano
2021-01-06  9:52       ` Takashi Yano
2021-01-07  8:38         ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-07  9:05           ` Takashi Yano
2021-01-07  9:39             ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-01-07 14:39               ` [cygwin] " Jason Pyeron
2021-01-07 15:00                 ` Takashi Yano
2021-01-07 16:49                   ` [cygwin] jansi adds spaces to output running maven on java in w10 Brian Inglis
2021-01-07 17:54                     ` Jason Pyeron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a62b788116ea47adb39e160d01404216@BELBRU-EXMP101.eeas.europa.eu \
    --to=panagiotis.kavalagios@ext.eeas.europa.eu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).