Le ven. 10 févr. 2023 à 21:57, Piotr P. Karwasz <piotr.karw...@gmail.com> a
écrit :

> Hi Romain,
>
> On Fri, 10 Feb 2023 at 21:19, Romain Manni-Bucau <rmannibu...@gmail.com>
> wrote:
> > Will likely not work until done on the jvm with line.separator system
> prop
> > directly due to a lot of things or means you limit the plugins you use a
> > lot so I think jvm.config is the way to go or you hack wrapper commited
> > launcher scripts to force it in MAVEN_OPTS.
>
> Hacks in the Maven Wrapper scripts is what I currently use, but that
> is not very proper and it works only if the user runs the potentially
> untrusted Maven Wrapper instead of a local Maven installation.
>
> The current `mvn` script removes all line breaks from `jvm.config`:
>
>
> https://github.com/apache/maven/blob/9b58d2bad23a66be161c4664ef21ce219c2c8584/apache-maven/src/bin/mvn#L172
>
> therefore it is impossible to set `line.separator` in it.
>

This part still needs enhancements and this is what I would work on instead
of duplicating a solution IMHO.


> That is why I would prefer if Maven did set `line.separator`
> programmatically using some other system property that can be more
> easily set.
>

Needs to be done before System class is init so almost impossible until you
use a javaagent which could do the trick if added in the distro if you want
to do some tests. Can be a way to fix the jvm.config handling but can also
require native code to be eager enough :s.


> Piotr
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to