maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MNG-6115) Add Jansi native library search path to our start scripts to avoid extraction to temp file on each run
Date Sun, 05 Mar 2017 10:53:32 GMT

    [ https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896173#comment-15896173
] 

Hervé Boutemy commented on MNG-6115:
------------------------------------

we definitely don't live in the same world when we evaluate complexity and feasibility
Then IMHO, the best thing is just to ignore the fact that there is an extraction on each run:
other people using JAnsi don't care and everything works great for them.
Let's remove this optimization that only gives us headaches

> Add Jansi native library search path to our start scripts to avoid extraction to temp
file on each run
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6115
>                 URL: https://issues.apache.org/jira/browse/MNG-6115
>             Project: Maven
>          Issue Type: Improvement
>          Components: Bootstrap & Build, Command Line
>            Reporter: Michael Osipov
>            Assignee: Hervé Boutemy
>             Fix For: 3.5.0-alpha-2
>
>
> By default Jansi extracts the native, shared library to temp which results in unnecessary
file I/O and a huge amount of temp files when Maven is run very often. One can avoid that
by adding {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib/ext}} to the start script. The user has
to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the overhead.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message